David Lord  writes:

> John Devereux wrote:
>> "Dave Liquorice"  writes:
>>
>>> On Thu, 22 Oct 2009 12:10:50 +0100, John Devereux wrote:
>>>
>>>> We have had this for months now, with these problems for many or
>>>> most weekends and many evenings. I am getting a lot of pressure to
>>>> change providers, I think one more "weekend" blip should do
>>>> it. (For us the evenings and weekends are the *worst* times for
>>>> you to to schedule your maintenance, since noone is there to
>>>> reboot the router and of course there is no technical support
>>>> either).
>>> Very good points. Maybe an weekly "at risk" period from 1000 to 1100
>>> on a Tuesday morning would be better?
>>>
>>> As a short term quick 'n dirty solution how about puting the router
>>> on a time switch that turns it off for a minute in the we small hours
>>> every night?
>>
>> Historically the problem has been that the router does not always
>> reconnect - it stays stuck on 0.0.0.0. Recently I manually set the WAN
>> address, and that seemed to cure that problem for a week. But last night
>> it again did not reconnect until power-cycled this morning.
>>
>>> Or for a longer term soultion feed it through a power
>>> switch that you can dial into over the phone line. I think there are
>>> quite cheap single socket ones available that respond to DTMF tones,
>>> so you could do it from your mobile whilst down the pub...
>>
>> Hmmm, good idea. Did not know this was available, will look into it.
>
> I've been using manual adsl stop then restart without power
> cycling but was away from system at start of both outages so
> need scripts to automate this for aaisp supplied Conexant
> r-adsl-c1 and/or Billion 5200S. If someone has already got
> this working it would save me some hacking.

I never thought of *that* either, never used the telnet/ssh admin
interfaces.

-- 

John Devereux