Some things you might want to look at:
Is the Linux box sending any traffic (look at the stats in ifconfig)?
Does a packet sniffer like http://www.ethereal.com/ give any clues as to the
type of traffic on the network?
Does the same thing occur if you run less processes, e.g. boot into run level
1 or 3?
Are there any processes consuming an unreasonable amount of CPU time on the
Linux box?
Is there a process which is being restarted many times a second, so top or ps
shows a radiply increasing PID?
It could be some network-aware process which has got stuck in a tight loop
sending requests to your windows box, e.g. a DHCP client.
I mention the DHCP client specifically because they sometimes get upset if you
don't enable some specific kernel networking options like CONFIG_PACKET or
CONFIG_FILTER & WinRoute might be acting as the DHCP server.
Jon
> Some things you might want to look at:
> Is the Linux box sending any traffic (look at the stats in ifconfig)?
> Does a packet sniffer like http://www.ethereal.com/ give any clues as to the
> type of traffic on the network?
> Does the same thing occur if you run less processes, e.g. boot into run level
> 1 or 3?
> Are there any processes consuming an unreasonable amount of CPU time on the
> Linux box?
> Is there a process which is being restarted many times a second, so top or ps
> shows a radiply increasing PID?
nope, nothing like that. Running just a bare minimum...
> It could be some network-aware process which has got stuck in a tight loop
> sending requests to your windows box, e.g. a DHCP client.
> I mention the DHCP client specifically because they sometimes get upset if you
> don't enable some specific kernel networking options like CONFIG_PACKET or
> CONFIG_FILTER & WinRoute might be acting as the DHCP server.
Yes, you might be right. WinRoute is running as DCHP for the network,
and the problems do start as soon as Linux tries to lease an IP...
hm..
> Jon
--------
PGP public key: https://tnonline.net/secure/pgp_key.txt
On Fri, 7 Mar 2003, Anders Widman wrote:
>Yes, you might be right. WinRoute is running as DCHP for the network,
>and the problems do start as soon as Linux tries to lease an IP...
>hm..
If you are using DHCP, it is critical that every machine have a correctly
set clock (see also: xntpd) Otherwise, the client may see the lease expire
before it requested it. (what happens in such a case varies with the software
and version.)
--Ricky
> On Fri, 7 Mar 2003, Anders Widman wrote:
>>Yes, you might be right. WinRoute is running as DCHP for the network,
>>and the problems do start as soon as Linux tries to lease an IP...
>>hm..
> If you are using DHCP, it is critical that every machine have a correctly
> set clock (see also: xntpd) Otherwise, the client may see the lease expire
> before it requested it. (what happens in such a case varies with the software
> and version.)
Yes, but everything works very good with 2.4.x kernels (all I have
tested so far). So the problems comes with 2.5.64.. And, there is not
much network traffic either when this happens...
> --Ricky
--------
PGP public key: https://tnonline.net/secure/pgp_key.txt