What kind of NIC's are we talking about? And how do we know that it's not
your ISP that's blocking the pings? Where do the traceroute's end? A
traceroute when it works and when it fails would be usefull here. Also my
ISP changed routers last summer and they now block all pings & traceroutes
from the outside world. It's also possible that your ISP has timeouts
against keeping track a route to your linux gateway and that sending a ping
is just refreshing their router tables.
Lyle
-----Original Message-----
From: AS T [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 28, 2000 12:18 PM
To: [EMAIL PROTECTED]
Subject: [expert] Network goes away after some idle time
I have the following problem on my linux gateway
machine (at my home).
The machine has two NIC cards. Eth0 is DHCP via adsl.
Eth1 has static ip for my internal network. IP_MASQ
is on to forward packets from my internal network.
Everything works nicely, except that if I went to work
and tried to ping my home (gateway) machine I notice
that the ping does not "always" respond.
I tried to track this and found out that eth0 seems to
"fall a sleep" once in a while.
However, my internal network has never had any problem
getting out. All I can say is that once eth0 falls a
sleep I would have to try later and it will somehow
wake up by itself (no reboot or anything is required
to get to work again, just waiting about 10-30
minutes). APM is turned off on the BIOS and the OS.
The only way I was able to remedy this is to have the
gateway machine ping an external site (ex.
www.yahoo.com)
every 1 minute. With the ping on, I can alawys get to
my gateway machine from work. I have few peopel on
the web that have the same problem and none could
figure out what the story is.
Any help is highly appreciated.
Thansk
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
