Re: network dropouts

["Jan Kundrát" <jan.kundrat@fzu.cz>]

 > My guess would be that the bridge code is receiving carrier-change
 > events from eth0. This causes it to put eth0 in disabled state for a
 > while.
 >
 > One way to check this would be to add some printk()'s to
 > net/bridge/br_notify.c and see whether you are getting NETDEV_CHANGE
 > or NETDEV_DOWN events. If so, it may be that your physical connection,
 > or your router/switch/hub, is a bit dodgy.
 >
 > None of the other paths via which the interface may get disabled seem
 > very likely to occur, but we can look at those if it doesn't appear
 > that you are getting NETDEV events.

Sorry for delay, we had had some problems with our mailserver. I'll try 
if I'm able to implement what you're talking about :-)

jkt

-- 
cd /local/pub && more beer > /dev/mouth



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/