19 public posts in this discussion.
anyone else having hassles?
Reply from 203.16.214.17: bytes=32 time=92ms TTL=60
Reply from 203.16.214.17: bytes=32 time=138ms TTL=60
Reply from 203.16.214.17: bytes=32 time=92ms TTL=60
Reply from 203.16.214.17: bytes=32 time=89ms TTL=60
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 138ms, Average = 102ms
C:\Documents and Settings\aaron>
Yep, Cas exchange. Re issuing ticket with node yet again....
omg... you have got to be F*cking kidding me
...
<stupidity>
BEHIND THE SCENES AT THE PROBLEM|
________________________________|
asshat no1# hmm looks like theres a problem should we fix it
asshat no2# na i wanna break the record of tickets we got last time :D just leave it its not like there gonna notice.
____________
</stupidity>
submitted too
here is the link to support if you need it
https://secure.internode.on.net/webtools/support
want me to setup a scheduled task that refiles that ticket every month?
Quote from Aegis;336415:
want me to setup a scheduled task that refiles that ticket every month?
sounds like it might make life easier
i'll look at their login setup tonight to see what i can rig :)
I seriously hate you for this news insid, great way to start teh weekend o pwning- "Hi your ping rate is f****d!! have a nice day" ........ :(
on that note submitting helpdesk in t minus 1 minute
Support request 1114155 submitted.
So what is a suitable ping for gaming?
Depends if you can spray - and/or are good at predicting where a person will be slightly into the future. Yesterday I was playing Crysis with 120 ping and still got plenty of kills - smg + lots of ammo = cant miss lol.
Id prefer to play with a ping of around 5-10 ( this will never happen for me up in darwin on southern servers) so i settle for 50-80ish, which keeps me with in the top 15 ranks on my clan server.
But when you hit 140-160ish and facing off against someone on a 5-15 ms ping, it generally sh1ts me to tears - for a number of reasons .
anything over 100ms - may aswell just spray and pray
- and now you know why i sucked in CS:S at that DGA i made it to last year ;P
just noticed the extra nodes added to the route darwin has to take to internode.... and one with a ping of a 99....
Tracing route to internode.on.net [203.16.214.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxxxxxxxx [xxxxxx]
2 <1 ms <1 ms <1 ms xxxxxxx
3 <1 ms <1 ms <1 ms xxxxxxx
4 89 ms 88 ms 89 ms 172.18.113.7
5 88 ms 89 ms 88 ms 172.18.72.30
6 88 ms 88 ms 89 ms 61.9.225.200
7 89 ms 89 ms 89 ms TenGigabitEthernet7-3.way21.Adelaide.telstra.net
[165.228.157.77]
8 88 ms 89 ms 89 ms GigabitEthernet0-1.way27.Adelaide.telstra.net [2
03.50.120.37]
9 90 ms 90 ms 91 ms optus3.lnk.telstra.net [139.130.237.10]
10 90 ms 91 ms 89 ms 61.88.221.51
11 94 ms 93 ms 91 ms 61.88.221.51
12 99 ms 98 ms 99 ms internodesystemspl.optus.net.au [59.154.0.18]
13 94 ms 91 ms 91 ms po2.cor3.adl2.internode.on.net [203.16.212.155]
14 95 ms 93 ms 94 ms corp.internode.on.net [203.16.214.17]
Trace complete.
ok now for those who do care and can explain this please do so..
according to my trace route im actually connecting through america twice then back to Australia links below..
heres the trace
------------------------------------------------------
Tracing route to internode.on.net.au [203.16.214.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxxxxxxx
2 <1 ms <1 ms <1 ms xxxxxxxxxxx
3 <1 ms <1 ms <1 ms xxxxxxxxxxx
4 90 ms 90 ms 90 ms 172.18.113.7
5 89 ms 89 ms 89 ms 172.18.72.30
6 88 ms 89 ms 96 ms 61.9.225.200
7 89 ms 88 ms 89 ms tengigabitethernet7-3.way21.adelaide.telstra.net
[165.228.157.77]
8 95 ms 91 ms 89 ms gigabitethernet0-1.way27.adelaide.telstra.net [2
03.50.120.37]
9 96 ms 96 ms 95 ms optus3.lnk.telstra.net [139.130.237.10]
10 96 ms 94 ms 97 ms 61.88.221.51
11 92 ms 95 ms 93 ms 61.88.221.51
12 95 ms 96 ms 94 ms internodesystemspl.optus.net.au [59.154.0.18]
13 161 ms 98 ms 98 ms po2.cor3.adl2.internode.on.net [203.16.212.155]
14 103 ms 96 ms 98 ms corp.internode.on.net [203.16.214.17]
Trace complete.
----------------------------------------------
the disturbing part are the 2 ip addresses 172.18.113.7 and 172.18.72.30 according to 'ipligence.com' both these ip's are located in the US.... can someone please confirm this by doing a tracert to internode.on.net.au in cmd and posting the results...
if anyone can correct me please do so (regarding the ip's of course)
not me.
Tracing route to internode.on.net.au [203.16.214.17]
over a maximum of 30 hops:
1 2 ms 14 ms 17 ms 192.168.1.1
2 100 ms 95 ms 92 ms lns10.adl6.internode.on.net [203.16.215.186]
3 100 ms 91 ms 92 ms vl13.cor1.adl6.internode.on.net [203.16.213.166]
4 100 ms 100 ms 95 ms corp.internode.on.net [203.16.214.17]
Trace complete.
On the same 4 jumps to node and have the 100+ms ping.
Trace route for me is still only 4 hops away - but latency is still up the creek, even though i got a issue resolved email today - pricks.
@ Dragon - You do know you dont need to add .au to the end of the address right.... ;)
Have mentioned that the latency issue is still in effect atm and prolly worth while following this up at their end.
well the tracert's ive done recently are from my work machine in somerville... there with bigpond..
we still get the jumps to america ect...
but at home i have the 4 usual jumps... however i cant see the 1st jump due to time an out..
anyone else getting this?