About the Darwin ping with iiSlamms

About the complaints obout the pings on iiSlamms being high to Internode Gaming Network....

There seems to be a case of some interesting routing, Dwn to Adl is straight forward, but the return path is a bit of a dogs breakfast with packets going Adl >> Syd >> Mel >> Adl >> Dwn

Darwin to Adelaide

Tracing route to games.internode.on.net [203.26.94.189]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 14 ms 13 ms nexthop.nt.iinet.net.au [203.206.222.254]
3 13 ms 13 ms 13 ms Fastethernet3-1.smi7.darwin.telstra.net [139.130.79.17]
4 14 ms 14 ms 15 ms FastEthernet4-0-0.smi-core1.Darwin.telstra.net [203.50.121.1]
5 48 ms 47 ms 47 ms Serial6-0-0.way-core2.Adelaide.telstra.net [203.50.116.101]
6 46 ms 47 ms 47 ms GigabitEthernet5-2.way18.Adelaide.telstra.net [203.50.119.28]
7 74 ms 74 ms 73 ms agilec1.lnk.telstra.net [139.130.66.2]
8 74 ms 74 ms 74 ms gi0-1.cor2.adl2.internode.on.net [203.16.212.152]
9 76 ms 74 ms 74 ms games.internode.on.net [203.26.94.189]

Trace complete.

Adelaide to Darwin

1 gig0-2-502.cor1.adl2.internode.on.net (203.26.94.253) 0.612 ms 0.521 ms 0.589 ms
2 gi0-3.bdr2.adl2.internode.on.net (203.16.212.145) 0.508 ms 2.444 ms *
3 pos2-0.bdr1.syd7.agile.on.net (203.16.212.33) 25.250 ms 26.495 ms *
4 gi0-2.cor1.syd3.agile.on.net (150.101.199.234) 26.998 ms 25.772 ms 25.215 ms
5 GigabitEthernet2-2.ken12.Sydney.telstra.net (139.130.249.5) 29.257 ms 27.528 ms 27.810 ms
6 10GigabitEthernet15-0.ken-core4.Sydney.telstra.net (203.50.20.1) 44.878 ms 27.472 ms 27.683 ms
7 10GigabitEthernet12-0-1.chw-core2.Sydney.telstra.net (203.50.6.42) 27.278 ms 27.501 ms 27.528 ms
8 Pos9-0.exi-core1.Melbourne.telstra.net (203.50.6.38) 27.440 ms 27.650 ms 27.469 ms
9 Pos3-0.way-core4.Adelaide.telstra.net (203.50.6.162) 27.610 ms 27.872 ms 27.491 ms
10 GigabitEthernet0-0-0.way-core2.Adelaide.telstra.net (203.50.116.254) 27.663 ms 27.645 ms 27.567 ms
11 Serial0-0-0.smi-core1.Darwin.telstra.net (203.50.116.102) 60.857 ms 60.144 ms 60.116 ms
12 FastEthernet0-1.smi7.Darwin.telstra.net (203.50.121.9) 64.040 ms 60.648 ms 61.223 ms
13 chime14.lnk.telstra.net (139.130.79.18) 61.800 ms 61.075 ms 61.113 ms

can you do some tracerts to other Gaming networks to see what they're like too, would be appreciated.

I can't really do a return trace from any other games network other then internode. ;)

yeah, what about some pings to GA,gamespace,iinet etc?

Quote from addas:
yeah, what about some pings to GA,gamespace,iinet etc?

Isn't this the same question... asked in another way... ie, twice?

And didn't he already answer you?

what i'm trying to imply is that maybe pings are the same as ADSL 1 (ie ~65ms) from here to the eastern state game networks and only the internode games servers experience have that 20ms diffference compared to ADSL 1.

All i'm interested is a ping to some ip's from GameArena/Gamespace which are in melbourne, rather than me just assuming they are automatically 20ms higher. Because if it's only node servers that have the higher latency that would not stop me from signing up to iiNET rather than if all gaming serers had higher pings.

Surely that makes some sense now.

At work so I can't double check, but I think we can safely assume that Melbourne based servers would be about 20ms higher then the Adelaide server. But I am more then willing to be pleasantly suprised. Will post some from home, if I can remember.

It isn't ADSL1 or ADSL2 that is the issue with the ping, it is the routing that the data is taking to and from the server that has the people on iiSlamms concerned about. If iiNet and Telstra and Node can get together and work on this we will have the same pings as anyone on the telstra equipment.

I have written to Internode at there feedback address, and I don't expect anything to really happen from it other then them suggesting that I churn to Internode to enjoy the full benefits of being a Internode customer. Can't really fault them on that response since it is part of there state aim of IGN.

cheers and yeah hopefully they can at least look into it nevertheless.

Aside from these discrepanacies in pings, how's ADSL 2 pulling up now after a few weeks?

Full speed ADSL1, roughly 750k/sec and 80k/sec upload with not fiddling about. Not worth the expense to get a ADSL2/2+ router/modem at the moment as most ftp server and bit toorents can't feed it at full speed.

Max BT speed so far 400k/sec :)

hmmmmmmm really interesting Jeats, that sorta sux with the routing... although i do hate my 50kb a second...

stupid bloody ping bs ..

i wish they could fix it

more of us signing up to the service and complaining about it should help :P, it's bareable yet when it can be 30% better, why not complain. Hopefully Cas exchange is migrated before the years end.

70ms ping is fine for nearly all FPS's specially if you are kicking back relaxing

so its 70ms ur getting ATM normally?

Quote from addas:
more of us signing up to the service and complaining about it should help :P, it's bareable yet when it can be 30% better, why not complain. Hopefully Cas exchange is migrated before the years end.

considering all the whinging that happens for dsl1 ping jumps and hikes, there is NO way they will do anything for dsl2 if they havnt fixed the routing the first time around.

40ms is normal for ADSL 1 from Darwin to Adelaide

the pings would be fine for me, only play wow and download

pings are okay only thing i might do is connect to my remote pc :S

Pings down south are still shifty, wouldn't mind if they fixed it up.

Having a hop in Darwin though is great. There are a few sites around the place which take advantage of it.

PING cdu.edu.au (138.80.128.42) 56(84) bytes of data.
64 bytes from falcon.ntu.edu.au (138.80.128.42): icmp_seq=0 ttl=58 time=19.0 ms
64 bytes from falcon.ntu.edu.au (138.80.128.42): icmp_seq=1 ttl=58 time=17.2 ms
64 bytes from falcon.ntu.edu.au (138.80.128.42): icmp_seq=2 ttl=58 time=17.2 ms
64 bytes from falcon.ntu.edu.au (138.80.128.42): icmp_seq=3 ttl=58 time=17.3 ms

--- cdu.edu.au ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 17.249/17.738/19.061/0.771 ms, pipe 2

Makes working on the uni servers from home a breeze :D

im getting 16 ms to that address :D

Umm my connection used to be shocking on internode servers 110, now its the best. 70-80. If you complain, thank u.

Sweeeeeet. They've fixed it :D

PING internode.on.net (203.16.214.17) 56(84) bytes of data.
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=0 ttl=56 time=51.4 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=56 time=52.2 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=56 time=52.6 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=56 time=51.6 ms

--- internode.on.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 51.493/52.008/52.674/0.497 ms, pipe 2

traceroute to internode.on.net (203.16.214.17), 30 hops max, 38 byte packets
1 divine.gateway (192.168.0.254) 2.156 ms 1.988 ms 2.002 ms
2 nexthop.nt.iinet.net.au (203.206.222.254) 18.853 ms 16.886 ms 16.868 ms
3 Fastethernet3-1.smi7.Darwin.telstra.net (139.130.79.17) 15.612 ms 15.472 ms 15.693 ms
4 GigabitEthernet0-1.smi-core3.Darwin.telstra.net (203.50.121.12) 16.867 ms 16.686 ms 16.374 ms
5 Pos1-0.fli-core2.Adelaide.telstra.net (203.50.116.49) 48.774 ms 49.899 ms 52.041 ms
6 GigabitEthernet5-2.way18.Adelaide.telstra.net (203.50.119.28) 49.632 ms 49.695 ms 49.801 ms
7 agilec1.lnk.telstra.net (139.130.66.2) 51.093 ms 53.447 ms 50.776 ms
8 gi0-1.cor2.adl2.internode.on.net (203.16.212.152) 51.144 ms 50.301 ms 50.429 ms
9 corp.internode.on.net (203.16.214.17) 50.058 ms 50.807 ms 51.576 ms

All on iiNet ADSL2 Darwin Exchange

They have pushed back Casuarina iiNet DSLAM upgrade until 1st qtr 2006.

yeah shame, better be towards the start of next year too...has iiNET adsl2 lived up to what you guys thought and wished for so far??

first ping i got was 56 but rest were 300 bloody leechers :P

I'm getting constant 46 ping to the node servers now.