Michael Weickel wrote: >All what you need to do is to ensure, that your access ports in >Netgear will tag traffic well.
I've seen problems before when setting up VLANs. There are often two different places the ports must be configured, and it's not always obvious that this is the case. Yes I've learned this the hard way :-/ Typically there can be a screen where ports are made members of the VLANs, and configured as tagged/untagged. This covers OUTBOUND packets. There is then often a different screen where it is configured what the switch does with untagged packets arriving inbound on the port. If this isn't configured, then untagged packets (which will be all packets if the port is configured as untagged) arriving from connected devices will be put into the default VLAN which is (as you say) normally VLAN1). Separate to this, the trunk port may well be configured to leave packets from VLAN1 as untagged even though it is a trunk port that should tag all outbound packets. So several traps for the novice here. I'd suggest going back and re-checking the switch config - looking for these specific points. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
