|
Networking daemons going to sleep?
I have a RedHat 9 machine which is primarily intended to be a server but which also has KDE installed on it. It participates happily on my wireless network - I'm using the Linuxant wrapper for the NDIS driver that came with the adapter. However...
Every time I come to comunicate with the machine after some small period where there has been no communication (eg, if I haven't logged into it in the past 5 minutes), it doesn't seem to be on the network at all. I can't log into it, can't FTP into it, can't even ping it. I then discovered that if I put a huge timeout value on a ping (say, 30000ms) and then repeatedly ping it, after a few attempts it will suddenly spring back to life (for example, this is the output from Windows ping):
C:\>ping -w 30000 192.168.0.73
Pinging 192.168.0.73 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.73:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ping -w 30000 192.168.0.73
Pinging 192.168.0.73 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.73: bytes=32 time=9ms TTL=64
Reply from 192.168.0.73: bytes=32 time=3ms TTL=64
Reply from 192.168.0.73: bytes=32 time=5ms TTL=64
Ping statistics for 192.168.0.73:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
It will now be absolutely fine on all protocols (well, SSH and FTP are the only two I've tried) as long as I keep communicating with it. As soon as I stop for a few minutes, it goes back into suspended animation...
If I look on the machine itself I can see that all the daemons are up and running throughout all this.
Any ideas? Am I right in thinking this is a core Linux thing, or should I be looking suspiciously at the Linuxant/NDIS combo?
TIA,
Wayne
|
