Re: network problem

[Thiemo Seufer <ths@networkno.de>]

Chris Gebhardt - VIRTBIZ Internet Services wrote:
> Thiemo Seufer wrote:
> >Johan Arens wrote:
> >
> >>Hi Guys
> >>
> >>I got a strange problem with my qube2.
> >>
> >>I use it to connect 2 different networks, the final goal is to do a 
> >>firewall
> >>with it.
> >>
> >>The problem is, if I start a large transfert from the network connected to
> >>eth1 to the network under eth0, all the connections to and from eth0 are
> >>becoming extremly slow : ping with more than 500.000 ms, impossible any 
> >>more
> >>to open a connection with ssh,...
> >>
> >>However, if I do a reset of the network, with /etc/init.d/network restart,
> >>the interface become normal again.
> >>
> >>I've found this in syslog :  kernel: NETDEV WATCHDOG: eth0: transmit timed
> >>out
> >>
> >>My kernel is  2.4.27-r5k-cobalt.
> >
> >
> >What is the exact version of the kernel package? You can find out via
> >
> >    dpkg -l 'kernel-image-*' |grep ^ii
> >
> >The latest version (on unstable 2.4.27-11.040815-2, on sarge
> >2.4.27-10.sarge1.040815-1) has a small fix which is supposed to address
> >this problem.
> >
> >
> >Thiemo
> >
> >
> 
> Do the latest versions also avoid the issue where the network would lock 
> up uncontrollably after a period of time?  We have stayed back with 
> kernel-image-2 2.4.27-8.04081 because it is reliable on the network.

AFAIK 2.4.27-8.04081 is not reliable when the Cobalt is used as a router
(i.e. traffic on both interfaces). -10 was supposed to fix that, but
broke networking on older hardware completely. -11 or -10.sarge1 should
work in all cases.


Thiemo