> > > > > Hi, > > > > > > I have been looking at this and on eth3 I see this > > > > > > 17:10:25.355276 vlan 40, p 0, IP 135.196.XXX.XX.5000 > > > 192.168.40.88.5000: > > > UDP, length 11 > > > 17:10:26.014292 > > > 17:10:26.371019 IP 135.196.XXX.XX.5000 > 192.168.20.30.5000: UDP, > > length > > > 11 > > > 17:10:26.371446 IP 192.168.20.30.5000 > 135.196.XXX.XX.5000: UDP, > > length > > > 10 > > > > > > I still do not understand why the packets do not go over the > > > correct > > vlan > > > interfaces and bridge. > > > > > > > (I haven't followed all of this thread so apologies if it's already > > been > > covered) > > > > You do have the correct brouting rules in place don't you? eg: > > > > ebtables -t broute -A BROUTING -p 802_1Q -i eth0 -j DROP > > > > This makes sure that the 802.1q tagged packets coming in on eth0 are > > not sent over the bridge as is, but are 'routed' internally to the > > vlan code, where they are decapsulated and then maybe routed to bridges. > > > > I was not aware that, that was required. I assumed that since I had > the eth0.40 and eth3.40 set-up then the packets would be routed > correctly, as I have. > > Eth0---------br0------------eth1 > Eth0.40------b1-------------eth1.40 > > So do I need to add in the ebtables rule? > That does seem to fix it with the ebtables rule. I now see the traffic going over the bridge, I will have to wait till Monday to fully check that it is working. I can also now see the traffic going over br1 in iptables but not br0 which is strange. Thanks, Adam ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. http://www.mettoni.com **********************************************************************
