[plug] Please help.. i'm desperate

[Steve Boak]

On Monday 22 September 2003 07:19, Nathan D wrote:
> On Mon, 22 Sep 2003 06:30:34 +0800, Daniel Pearson wrote:
> >Ok, a brief update on things.
> >
> >Last night, a mate brought around an old old cable, instead of
> > being an rj11 cable with an adapter to plug into the 600 series
> > socket it has the actual 600 series plug on it. Since then, i've
> > only experienced one disconnection, but when reconnected gained
> > the *exact* same ip (one in a million? heh).
>
> Can only hope you are onto something here?
> The information about the same IP might be something relevant.  If
> you check the iinet toolbox for your connection history and find
> multiple sequential connections with the same IP, this is bogus
> information(IMHO).  I have queried this with the iine(p)t support
> and they have assured me that it is correct information.  The
> toolbox history has shown disconnections of up to a few hours and
> then retaining the same IP, but my IPCop box (BIPAC711CE in bridged
> mode) shows a constant connection of several days.  Sorry iinet,
> but I have faith in my own logs. iiNet have also been having issues
> with routers lately where they lose all connectivity (internal and
> external) but you still maintain a connection.  (My IRC log shows
> this happening from 01:03 to 01:28 this morning). Not sure if any
> of this is relevant or not?  My Billion has been in bridged mode
> since the day I got my connection so I have no stats or info to
> post from it :(
>

I had *huge* problems with losing IP but staying connected, in June 
through Westnet, eventually changed dialup numbers (seems to be a 
regular thing these days) to fix the problem. As usual, nothing ever 
said about what the problem was. I was also getting 'impossible' ping 
times, the following times ARE accurate, as timed by my own perfectly 
good watch...

PING westnet.com.au (203.10.1.20) from 202.72.174.186 : 56(84) bytes 
of data.
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=1 ttl=123 
time=169 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=2 ttl=123 
time=189 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=3 ttl=123 
time=199 ms
64 bytes from 203.10.1.20: icmp_seq=4 ttl=123 time=4439 ms
64 bytes from 203.10.1.20: icmp_seq=5 ttl=123 time=26489 ms
64 bytes from 203.10.1.20: icmp_seq=6 ttl=123 time=65279 ms
64 bytes from 203.10.1.20: icmp_seq=7 ttl=123 time=71779 ms
64 bytes from 203.10.1.20: icmp_seq=8 ttl=123 time=73939 ms
64 bytes from 203.10.1.20: icmp_seq=9 ttl=123 time=161209 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=10 ttl=123 
time=160220 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=11 ttl=123 
time=159249 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=12 ttl=123 
time=158260 ms
64 bytes from wombat.wn.com.au (203.10.1.20): icmp_seq=13 ttl=123 
time=149809 ms

Logging with tcpdump, I got some icmp responses 58 minutes after the 
request was sent! As far as I know the problem just 'went away', I 
suspect after an upgrade of some sort at Westnet.

Steve

-- 
'What is worth doing and what is worth having?'
I would like to say simply this.
"It is worth doing nothing and having a rest."