[Bridge] Re: [more info] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991!

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

 



On Tuesday 02 September 2003 19:45, Stephen Hemminger wrote:
> > Looks like bridging is taking an input packet, transmitting it but not
> > initializing skb->csum, skb->ip_summed, and other fields before doing
> > so.
> >
> > Definitely a bridging bug.
>
> It is actually a bridging-filter bug, since the bridge layer is at level 2
> it doesn't know anything about IP.

A message ([Bridge] Re: [2.4.22] bad interaction between e100 and bridge: BUG 
at dev.c:991!) on the bridge list said this:

<quote>
> setup & how to reproduce:
> HP Netserver 2000 with 2 onboard e100 NICs. Both are connected to the same 
hub.
> Add both eth0 and eth1 to the same bridge. Pull the plug on eth0. 
> Wait till the bridge is about to enter forwarding state on eth1.
> 
> I have reproduced this with earlier kernels (2.4.20+) too but they 
> were heavily patched. This is a pristine 2.4.22.
> 
> Strange but true: This works when using eepro100 insted of e100.
<unquote>

A pristine 2.4.22 doesn't have bridge-netfilter. I don't see how 
bridge-netfilter would be involved anyway, altering a packet doesn't 
automagically trigger checksum recalculation.

cheers,
Bart



[Index of Archives]     [Netdev]     [AoE Tools]     [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