paradise dicey
64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms 64 bytes from 203.96.152.127: icmp_seq=1459 ttl=55 time=3615 ms 64 bytes from 203.96.152.127: icmp_seq=1460 ttl=55 time=2623 ms 64 bytes from 203.96.152.127: icmp_seq=1461 ttl=55 time=1644 ms -- 64 bytes from 203.96.152.127: icmp_seq=26 ttl=55 time=5928 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=27 ttl=55 time=4480 ms 64 bytes from 203.96.152.127: icmp_seq=28 ttl=55 time=3487 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=29 ttl=55 time=7652 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=30 ttl=55 time=7016 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=31 ttl=55 time=6888 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=32 ttl=55 time=5341 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=33 ttl=55 time=4452 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=34 ttl=55 time=8980 ms 64 bytes from 203.96.152.127: icmp_seq=35 ttl=55 time=13389 ms 64 bytes from 203.96.152.127: icmp_seq=36 ttl=55 time=13589 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. Wesley Parish -- Clinersterton beademung, with all of love - RIP James Blish - Gaul is quartered into three halves. Things which are impossible are equal to each other. Guerrilla warfare means up to their monkey tricks. Extracts from Schoolboy Howlers - the collective wisdom of the foolish. - Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.
Re: paradise dicey
2008/9/20 Wesley Parish wrote: 64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms [snip] 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. I get: PING www.paradise.net.nz (203.96.152.127) 56(84) bytes of data. 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=1 ttl=53 time=78.7 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=2 ttl=53 time=80.1 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=3 ttl=53 time=78.3 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=4 ttl=53 time=81.5 ms --- www.paradise.net.nz ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3017ms rtt min/avg/max/mdev = 78.349/79.713/81.578/1.309 ms I'm with Orcon. They're OK when my ADSL connection isn't down (which is too often but I haven't tested with another router). Yuri
Re: paradise dicey
On Sat, 20 Sep 2008 22:09:24 +1200 Wesley Parish [EMAIL PROTECTED] wrote: 203.96.152.127: icmp_seq=36 ttl=55 time=13589 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. Wesley Parish Does ifconfig show any errors, or does a 3 fingered salute to the router help?? -- Steve [EMAIL PROTECTED]
Re: paradise dicey
Quoting Steve [EMAIL PROTECTED]: On Sat, 20 Sep 2008 22:09:24 +1200 Wesley Parish [EMAIL PROTECTED] wrote: 203.96.152.127: icmp_seq=36 ttl=55 time=13589 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. Wesley Parish Does ifconfig show any errors, or does a 3 fingered salute to the router help?? I'm on dialup - one of the people supporting telstra-clear's gambling on the investment markets and government bailouts, I expect. ifconfig: ppp0 Link encap:Point-to-Point Protocol inet addr:210.246.27.44 P-t-P:202.0.46.83 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1159 errors:1 dropped:0 overruns:0 frame:0 TX packets:1379 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:641637 (626.5 KiB) TX bytes:196778 (192.1 KiB) Looks okay to me. I'm thinking it's probably also telecom's gambling on the investment markets and government bailouts - ie, their total lack of interest in maintaining their copper megamiles for which they are so happy to take an arm and a leg for. But I've already lost two goes at downloading the zarafa source code - a mere 2 megabytes. And it's starting to piss me off royally. I'll probably ring up both telstraclear and telecom in the morning and give them rockets about their incompetence. Wesley Parish -- Steve [EMAIL PROTECTED] Sharpened hands are happy hands. Brim the tinfall with mirthful bands - A Deepness in the Sky, Vernor Vinge I me. Shape middled me. I would come out into hot! I from the spicy that day was overcasked mockingly - it's a symbol of the other horizon. - emacs : meta x dissociated-press
Re: paradise dicey
But I've already lost two goes at downloading the zarafa source code - a mere 2 megabytes. And it's starting to piss me off royally. I'll probably ring up both telstraclear and telecom in the morning and give them rockets about their incompetence. But it was mentioned on either /. or LWN earlier today, I can't remember which. So I'm not at all surprised that the connection is flakey. I'll get it for you if you want. On 9/20/08, Wesley Parish [EMAIL PROTECTED] wrote: Quoting Steve [EMAIL PROTECTED]: On Sat, 20 Sep 2008 22:09:24 +1200 Wesley Parish [EMAIL PROTECTED] wrote: 203.96.152.127: icmp_seq=36 ttl=55 time=13589 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. Wesley Parish Does ifconfig show any errors, or does a 3 fingered salute to the router help?? I'm on dialup - one of the people supporting telstra-clear's gambling on the investment markets and government bailouts, I expect. ifconfig: ppp0 Link encap:Point-to-Point Protocol inet addr:210.246.27.44 P-t-P:202.0.46.83 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1159 errors:1 dropped:0 overruns:0 frame:0 TX packets:1379 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:641637 (626.5 KiB) TX bytes:196778 (192.1 KiB) Looks okay to me. I'm thinking it's probably also telecom's gambling on the investment markets and government bailouts - ie, their total lack of interest in maintaining their copper megamiles for which they are so happy to take an arm and a leg for. But I've already lost two goes at downloading the zarafa source code - a mere 2 megabytes. And it's starting to piss me off royally. I'll probably ring up both telstraclear and telecom in the morning and give them rockets about their incompetence. Wesley Parish -- Steve [EMAIL PROTECTED] Sharpened hands are happy hands. Brim the tinfall with mirthful bands - A Deepness in the Sky, Vernor Vinge I me. Shape middled me. I would come out into hot! I from the spicy that day was overcasked mockingly - it's a symbol of the other horizon. - emacs : meta x dissociated-press -- Sincerely etc. Christopher Sawtell
Re: paradise dicey
On Sat 20 Sep 2008 23:32:36 NZST +1200, Wesley Parish wrote: But I've already lost two goes at downloading the zarafa source code - a mere 2 megabytes. And it's starting to piss me off royally. I'll probably ring up both telstraclear and telecom in the morning and give them rockets about their incompetence. Unfortunately, giving the call centre droid an earful about their employer's incompetence isn't likely to achieve much. It's not that person's fault. A formal compaint might get escalated, but then some statistics to back it up with would add a lot of weight. Failure to download 2MB twice in a row is pretty bad, but if you've tried that only with one and the same server you know as well as I do what the obvious reply is going to be, and we both know it's the correct one too. Telstra cable is going fine, but that's not helping you. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
Re: paradise dicey
On Sat, Sep 20, 2008 at 10:09 PM, Wesley Parish [EMAIL PROTECTED] wrote: 64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms 64 bytes from 203.96.152.127: icmp_seq=1459 ttl=55 time=3615 ms 64 bytes from 203.96.152.127: icmp_seq=1460 ttl=55 time=2623 ms 64 bytes from 203.96.152.127: icmp_seq=1461 ttl=55 time=1644 ms -- 64 bytes from 203.96.152.127: icmp_seq=26 ttl=55 time=5928 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=27 ttl=55 time=4480 ms 64 bytes from 203.96.152.127: icmp_seq=28 ttl=55 time=3487 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=29 ttl=55 time=7652 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=30 ttl=55 time=7016 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=31 ttl=55 time=6888 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=32 ttl=55 time=5341 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=33 ttl=55 time=4452 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=34 ttl=55 time=8980 ms 64 bytes from 203.96.152.127: icmp_seq=35 ttl=55 time=13389 ms 64 bytes from 203.96.152.127: icmp_seq=36 ttl=55 time=13589 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=37 ttl=55 time=14956 ms Anybody else getting this sort of crap from paradise.net.nz? I've been getting it for two nights now, and I'm getting sick of it. Wesley Parish no, from my woosh account: [EMAIL PROTECTED]:~$ ping www.paradise.net.nz PING www.paradise.net.nz (203.96.152.127) 56(84) bytes of data. 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=1 ttl=53 time=107 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=2 ttl=53 time=163 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=3 ttl=53 time=128 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=4 ttl=53 time=159 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=5 ttl=53 time=178 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=6 ttl=53 time=170 ms 64 bytes from www.paradise.net.nz (203.96.152.127): icmp_seq=7 ttl=53 time=150 ms --- www.paradise.net.nz ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 5999ms rtt min/avg/max/mdev = 107.125/151.071/178.587/23.311 ms
Re: paradise dicey
On Sun, 21 Sep 2008, Nick Rout wrote: On Sat, Sep 20, 2008 at 10:09 PM, Wesley Parish [EMAIL PROTECTED] wrote: 64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms 64 bytes from 203.96.152.127: icmp_seq=1459 ttl=55 time=3615 ms 64 bytes from 203.96.152.127: icmp_seq=1460 ttl=55 time=2623 ms 64 bytes from 203.96.152.127: icmp_seq=1461 ttl=55 time=1644 ms -- Wesley try this; ping -c 1 -R paradise.net.nz -R Record route.Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. Note that the IP header is only large enough for nine such routes. Many hosts ignore or discard this option. If your ISP supports this you can see the hop's taken to reach paradise,then you can test each hop with a ping to check latency. Cheers Ross Drummond
Re: paradise dicey
Hi, Even better, try traceroute This reports the time for each leg of the route taken by the icmp packets. This verifies there is (or is not) a problem in your setup. Derek. == On Sun, 21 Sep 2008, Ross Drummond wrote: On Sun, 21 Sep 2008, Nick Rout wrote: On Sat, Sep 20, 2008 at 10:09 PM, Wesley Parish [EMAIL PROTECTED] wrote: 64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms 64 bytes from 203.96.152.127: icmp_seq=1459 ttl=55 time=3615 ms 64 bytes from 203.96.152.127: icmp_seq=1460 ttl=55 time=2623 ms 64 bytes from 203.96.152.127: icmp_seq=1461 ttl=55 time=1644 ms -- Wesley try this; ping -c 1 -R paradise.net.nz -R Record route.Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. Note that the IP header is only large enough for nine such routes. Many hosts ignore or discard this option. If your ISP supports this you can see the hop's taken to reach paradise,then you can test each hop with a ping to check latency. Cheers Ross Drummond -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/
