Hi Peter, Thanks for the swift response, much appreciated. I have tried this several times, and again since reading your email. This does work in that vlan 1 gets including in the bridge. However it seems to have the effect of disabling traffic from any of the the vlan interfaces, eth0.x. So the bridge works for all traffic on vlans without eth0 in the bridge, and then just for vlan 1 when eth0 is added to the bridge. On closer inspection using brctl showmacs br0 I can see that this is not strickly true. When eth0 is in the bridge and I add new clients, I can see that they are being found on the port in the bridge that eth0 is on, not the correct sub interface as before. Has anyone experienced this before ? Again, many thanks - this is a very responsive mailing list ! Piccalo --- Peter Stuge <stuge-vlan@xxxxxxx> wrote: > On Fri, Oct 29, 2004 at 09:46:18AM +0100, liam sharp > wrote: > > I'm using setup 1b from the vlan FAQ. Eveything is > > working fine, except one thing. I'd like to be > able to > > communciate with my switches through the bridge, > not > > thought eth0. > > One solution is almost too simple; > > brctl add br0 eth0 > > But! You will probably want to set up some ebtables > rules so that not > just anyone can speak to the management VLAN. > > > Another, perhaps more elegant, suggestion is to pick > a separate VLAN > (1?) in your network for management use, and only > make selected > switch ports members of that VLAN. > > Then make a br1 bridge on your bridge box, with the > management VLAN > and eth0 as member interfaces. That way you'll be > able to reach eth0 > from "within" the network as long as you're > connected to a switch > port which belongs to the management VLAN. :) > > > //Peter > _______________________________________________ > Vlan mailing list > Vlan@xxxxxxxxxxxx > http://www.lanforge.com/mailman/listinfo/vlan > Send instant messages to your online friends http://uk.messenger.yahoo.com
