The problem you may be running into could be caused by the switches broadcasting spanning tree packets. These will be broadcast back to the switch causing some confusion. take a look at http://lists.osdl.org/pipermail/bridge/2005-October/001116.html a.gatta wrote: > Dear List, > I am experiencing problems bridging two vlans on a linux box running > debian. > > I have a single interface (eth0,Broadcom NetXtreme BCM5705M_2 with tg3 > module). > > This interface has a trunk to a catalyst switch. > > > I've created two virtual interface with vconfig: > > vconfig add eth0 608 > vconfig add eth0 609 > > At this point all is fully functional, I am able to see traffic on > those virtual interfaces and if I give them the ip stack I can use them. > > Then I decided two bridge the two virtual interfaces. > > So I created a bridge with brctl : > > brctl addbr br0 > > and I've added those virtual interfaces to the bridge : > > brctl addif br0 eth0.608 > brctl addif br0 eth0.609 > > Last thing I enable all the interfaces : > > ifconfig br0 up > ifconfig eth0.608 up > ifconfig eth0.609 up > > The first thing I noticed is that I cannot see any traffic on br0 > interface and also on the virtual interfaces. > > As far as I know the bridge code supports tagged packet but I am not > able to see any traffic on the interfaces. > > Moreover the tg3 module support natively vlan traffic. > > This is what I see on both br0 and virtual interfaces after I add them > to the bridge : > > 14:23:22.539413 00:0a:b7:23:61:97 > 01:00:0c:cc:cc:cd SNAP Unnumbered, > ui, Flags [Command], length 50 > 14:23:22.540865 00:0a:b7:23:61:97 > 01:00:0c:cc:cc:cd SNAP Unnumbered, > ui, Flags [Command], length 50 > > Any ideas ? > -- Alvin Starr || voice: (416)585-9971 Interlink Connectivity || fax: (416)585-9974 alvin@xxxxxxxxxx ||
