Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
well this has nothing at all to do with vlans, you need to actually explain your network architecture. generally that too shouldn't matter hugely if you only have one internet connection with all traffic routing towards it. that's just a generic squid install.
I want to filter the traffic on vLAn basis, example i may add restriction to vlan 10 and I may not add restriction to vlan 20 I may just need to monitor the incoming and outgoing traffic at vlan 30 without restricting anything etc.
By the way can we monitor all the traffic just with iptables?
no, as above this isn't about vlans. you can't filter on "vlan 20" as this means nothing to a server. instead you'd filter on ip subnet, 192.168.1.0/24 etc...
So in this case it would mean that all the traffic thats coming/going to 192.168.1.0/24 would be monitored, well in that case would squid show me the source/destination IP in logs that of a vlan network as in vlan 20 or would it show me the 192.168.1.0/24 subnet Ip ?
Becasue it doesn't make lot of sense to monitor 192.168.1.0/24 subnet if I don't come to know which ip is accessing what url whether it be from any network.