John Weston <invalid@earlsway.invalid> writes:

> In article , "John Devereux" wrote:
>> 
>> Nix  writes:
>> 
>> > On 23 Oct 2009, John Devereux stated:
>> >> Well, right on schedule, it has gone off at 20:15 (Friday). And stayed
>> >> off. 
>> >
>> > 20:15? That's interesting. It went off for a hunk around 19:30 for me,
>> > but came back *on* at 20:11.
>> >
>> >> But since the usual suggestion is "turn the router off for 20 minutes"
>> >> probably not :(
>> >
>> > Get another router? Mine has reconnected flawlessly every time, even
>> > after the big LNS double-messup recently. Nothing special about it, just
>> > an AAISP standard one.
>> 
>> Hi,
>> 
>> It's already another router, changed it a couple of weeks ago, for ~3rd
>> time. New cable, connected directly to test socket.
>> 
>> > If it happens with several routers, perhaps it's something BT-related?
>> 
>> I think so, at least this time. It has been hard to prove up until
>> recently. It has been the combination of the AAISP disconnects plus the
>> failure by BT(?) to reconnect properly (0.0.0.0 IP).
>> 
>
>
> During the 20CN IPSC trial, I had a similar problem with failure to 
> login again after PPP drop.  Shaun investigated this with me and it was 
> determined that the encrypted password sent to AAISP from BT was 
> corrupt. This resulted in a "password incorrect" failure to login.  My 
> routers (Billion or ZyXEL) then went through what looked like a time-out 
> interval before trying again.  Sometimes this cycle was repeated for 
> several minutes before a good password was received.  Perhaps some 
> routers drop out of this retry cycle and fall back to needing a manual 
> restart?  We tried several types of password (short, long, complex, 
> simple) but the only way of ensuring a quick login was for Shaun to set 
> up for no password required at his end.

Thanks, perhaps we can try that too.

> I understood this problem was in the BT network and had been identified 
> and fixed before the end of the trial.  I've seen one or two long login 
> periods since, but assumed these where due to "genuine" problems, like 
> stuck sessions. :-) Most PPP drops and logins are now just a few 
> seconds.  I've also found setting my router's WAN address rather than 
> waiting for DHCP shaves a few seconds off the cycle.
>
> Does your Status/Log page at AAISP tell you anything significant?

Hi John,

Nothing significant to me...

Oct 23 20:14:56 clueless bgpfeed: xxxxxx@a Route 81.187.19.108/32 now down
Oct 23 20:14:56 clueless bgpfeed: xxxxxx@a Route 81.187.19.0/26 now down
Oct 23 20:14:56 clueless radius-acct: BBIP17484856 Stopped xxxxxx@a AdminReset 
Oct 24 11:54:00 clueless radius-auth: BBIP17484856 Platform b.gormless 217.41.221.142 xxxxxx@a 
Oct 24 11:54:00 clueless radius-auth: BBIP17484856 Accept 217.41.221.142 213.120.187.234 xxxxxx@a b.gormless txrate=7000000bps*95% linerate=7915000/7915000 MTU=1500 
Oct 24 11:54:00 clueless bgpfeed: xxxxxx@a Route 81.187.19.0/26 now 90.155.53.12
Oct 24 11:54:00 clueless bgpfeed: xxxxxx@a Route 81.187.19.108/32 now 90.155.53.12
Oct 24 11:54:03 clueless radius-acct: BBIP17484856 Start xxxxxx@a 213.120.187.234 MRU=1500 linerate=6650000/7915000

(xxxxxx represents our login)

We are working again for now, had to send someone in to flick the switch
since MD was jumping up and down.

-- 

John Devereux