[VLAN] Issue with Vlans and bridges

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 14, 2006 at 03:12:14PM +0100, Linux wrote:
>> If I run tcpdump on eth0.40 I only see the packets in one direction
>> but never see the return packets.

> In which direction do you see packets?

If I do the tcpdump on the eth0 interface I see this

23:43:53.869873 vlan 40, p 0, IP 192.168.40.3.5000 > 135.196.XXX.XX.5000:
UDP, length 13
23:43:53.892590 vlan 40, p 0, IP 135.196.XXX.XX.5000 > 192.168.40.3.5000:
UDP, length 6
23:43:54.074334 vlan 40, p 0, IP 192.168.40.6.5000 > 135.196.XXX.XX.5000:
UDP, length 13
23:43:54.101762 vlan 40, p 0, IP 135.196.XXX.XX.5000 > 192.168.40.6.5000:
UDP, length 6
23:43:54.369650 vlan 40, p 0, IP 192.168.40.3.5000 > 135.196.XXX.XX.5000:
UDP, length 13

If I do tcpdump on eth0.40 interface I see this

23:47:51.329939 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:47:51.829833 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:47:52.329773 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:47:52.821715 IP 192.168.40.12.5000 > 135.196.XXX.XX.5000: UDP, length 13

If I do tcpdump on eth3.40 interface I see this

23:48:46.638339 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:48:47.068323 IP 192.168.40.13.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:48:47.138406 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:48:47.191248 IP 192.168.40.3.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:48:47.638347 IP 192.168.40.6.5000 > 135.196.XXX.XX.5000: UDP, length 13

What I do not understand is why when the return packets are seen on a dump
of eth0 with a vlan 40 do they not should on dumps of eth0.40 or eth3.40

Both of these interfaces are on bridge br1 this is a dump of that bridge

23:50:48.995484 IP 192.168.40.7.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:50:49.267942 IP 192.168.40.4.5000 > 135.196.XXX.XX.5000: UDP, length 13
23:50:49.386119 IP 192.168.40.15.5000 > 135.196.XXX.XX.5000: UDP, length 13

>> Has anyone seen this before or does anyone know what could be at
>> fault?

> Assuming you have verified the two links individually first I think
> only firewall rules could cause a problem.

> If you haven't verified both links then maybe you're seeing the
> oversize packets problem. This happens with some NIC drivers in the
> kernel that do not accept packets larger than the maximum specified
> by the ethernet network (and that is usually the default in the NIC)
> - with 4 VLAN bytes added by the switch fullsize ethernet packets
> will be oversize when arriving to the card.

> Which card and driver are you using? I have great experience from
> e100/e1000 cards, they do not have this issue.

The network cards are intel cards, lsmod lists the e100 and e1000 driver.

Running on kernel 2.6.15-1 which is from the Debian testing branch.

>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they

> Please don't send confidential email to public mailing lists.

The footer is added at the mail gateway I have little control over it.

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
**********************************************************************


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]     [Video 4 Linux]

  Powered by Linux