----- Original Message ----- From: "Oleg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 8:10 AM Subject: [Bridge] 2.4.17 kernel panic...
> > Hi there! Hello, > Please help me with such problem: > I have bridge(s), kernel configuration is: > linux-2.4.17 + bridge-nf-0.0.5-against-2.4.17 + ebtablesv1.0_vs_nf-0.0.4 > When i try "ping xxx.xxx.xxx.xxx -s 20000" the bridge hangs, when it > recieve first reply from xxx.xxx.xxx.xxx host. If host is not exsist, & > bridge do not get any reply, the command "ping xxx.xxx.xxx.xxx -s 20000" > works without hangups. > Thanks in advance! > Regards, Oleg. I am experiencing this oops too. And with a size of around 5000 I get about 50% packet loss. Doing a ping xxx.xxx.xxx.xxx -s 20000 from a host through the bridge to another host also oopses the bridge box. Lennert: in net/ipv4/netfilter/ip_conntrack_standalone.c the function ip_refrag() is registered onto NF_IP_POST_ROUTING with priority NF_IP_PRI_LAST. So: this function will try to fragment stuff on the bridge POST_ROUTING hook. Is this healthy? Unfortunately I don't know enough of the bridge code and ip code to know this for sure. Also: is it healthy that connection tracking defragments the ip packets on the bridge PREROUTING hook? Doesn't this give problems if the bridge/router box has to bridge those frames (instead of route them)? cheers, Bart _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
