I fixed it by adding
*/2 * * * * /bin/ping -c 1 <router's ip> -q >/dev/null to a
to the crontab, and it's worked fine since (granted not very long, but
this was quite a reptitive thing).
On 1 Mar 1999, Jason L Tibbitts III wrote:
} The machine simply doesn't respond to any network traffic until it
} initiates some. After that it responds, but the connection is really
} sketchy. A ping out from the box shows lots of dropped packets, lots of
} dups (!) and on about every other reboot the round trip time will be on the
} order of 65000000 seconds. (I may have added a zero there; it's tough to
} get the actual text off of the box because the network is so spotty.)
Uh well, it might be the card. My stuff disappeared until the box started
talking, and I did get a lot of errors. Give the crontab-ping thing a
shot.
Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/