My adsl went down.  The router status mode alternated between ADSL_G and 
error.  After 50 minutes I rebouted the router and everything became OK.

For me, this is nightmare mode;  50 minutes seems long enough to wait 
to see if the problem is going to be sorted out from outside.  What 
happens when I'm not here to reboot the router?

-- 
Alan

( If replying by mail, please note that all "sardines" are canned.
   However, unless this a very old message, a "tuna" will swim right
   through. )

In article ,
	Alan Clifford <alan+sardines@purse-seine.net> writes:
> 
> 
> My adsl went down.  The router status mode alternated between ADSL_G and 
> error.  After 50 minutes I rebouted the router and everything became OK.
> 
> For me, this is nightmare mode;  50 minutes seems long enough to wait 
> to see if the problem is going to be sorted out from outside.  What 
> happens when I'm not here to reboot the router?

In my case, a cronjob runs every 15 minutes, retrieves some web pages
from the router's admin screens, and forces it to reboot if it doesn't
have a WAN IP address.

I have a couple of other situations I need to add to the cron job to
cover all bases. If the cron job can't contact the router at all, it
needs to do a mains power cycle (which the system has the capability
of doing). There are two known cases where my router gets into this
state.
1) After some months of being up, the web interface stops responding,
   although the rest of the router appears to continue to work fine.
   However, in this state, I can't tell if the router has a WAN IP.
2) After momentary (fraction of a second) power glitches, the router
   is usually left locked-up.

-- 
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]