Reporting Packetloss / Latency

[Tres]

You should let it run more cycles to get more reliable results. It seems like some of the packetloss occurs in your ISPs network, so you should probably contact them for starters. I think it was the core2.dca2 Hopone router that was defective according to the other thread.

Here is the reply i got from hopone when i contacted them:
Our network is secure and on non-publicly-routable IPs, so you will
be never able to ping it and thus will see 100% "packet loss" if you
try to ping any of our routers, or use a non-standard traceroute
application that runs pings vs. runs a normal traceroute.

What matters is your p.l. to the server - there is some here indeed,
but that is due to issues on your side, starting at the very first
hop, i.e.
1 194.145.148.170 brnt-bam-3.inet.ntl.com 3.9 210
240 280

You should work with your ISP and have them resolve your packet loss
issues, or if you are overloading your limited bandwidth connection,
then try using it less not to cause any packet loss on your side.

All is perfect on our side, the issues are only on your side.


I doubt that 'perfect' is true, since i've heard so many people complaining about hopone... With my isp, virgin media, being one of the biggest in the uk, i doubt there are any ploss issues on their side, or at least ones that they would be willing to fix (they have so many customers i find it unlikely they would do any major maintenance for me, any time i have contacted them in the past regarding speed / ploss issues, i just get told the problem is on my side and i get given the same old advice such as to check for viruses and make sure nothing (e.g microwaves) is interefering with my connection, which angers me.....
I haven't played in tw for over 3 weeks because of this ploss issue, all i can do is sit in spec, and if i can't fix it, i can't play :<

Considering all this, perhaps it would be best if i was to connect through a proxy, since i noticed there is a socks5 option in the client... Is this possible? i tried a wide variety of proxies with no success, just the same error message 4. Any suggestions welcome.

[Darkmoor]

Here is the reply i got from hopone when i contacted them:
Our network is secure and on non-publicly-routable IPs, so you will
be never able to ping it and thus will see 100% "packet loss" if you
try to ping any of our routers, or use a non-standard traceroute
application that runs pings vs. runs a normal traceroute.

What matters is your p.l. to the server - there is some here indeed,
but that is due to issues on your side, starting at the very first
hop, i.e.
1 194.145.148.170 brnt-bam-3.inet.ntl.com 3.9 210
240 280

You should work with your ISP and have them resolve your packet loss
issues, or if you are overloading your limited bandwidth connection,
then try using it less not to cause any packet loss on your side.

All is perfect on our side, the issues are only on your side.


I doubt that 'perfect' is true, since i've heard so many people complaining about hopone... With my isp, virgin media, being one of the biggest in the uk, i doubt there are any ploss issues on their side, or at least ones that they would be willing to fix (they have so many customers i find it unlikely they would do any major maintenance for me, any time i have contacted them in the past regarding speed / ploss issues, i just get told the problem is on my side and i get given the same old advice such as to check for viruses and make sure nothing (e.g microwaves) is interefering with my connection, which angers me.....
I haven't played in tw for over 3 weeks because of this ploss issue, all i can do is sit in spec, and if i can't fix it, i can't play :<

Considering all this, perhaps it would be best if i was to connect through a proxy, since i noticed there is a socks5 option in the client... Is this possible? i tried a wide variety of proxies with no success, just the same error message 4. Any suggestions welcome.

First, do a new trace with a few hundred cycles and post that.

Some packetloss is most likely from your ISPs network. It is a bit difficult to determine where exactly from that trace, but the 1.9 % from the second hop seem like it might carry till the end. The rest is possibly hopone/superb. There was a thread in the General Discussion forum regarding a problematic hop at hopone. Although any serious SP would have fixed it by now (a Cisco router never fails... HAH!).

You can use a proxy, if you can find one to use. Just keep in mind that it will further increase the latencies and could introduce more packetloss.

[Tres]

Bye

I guess there's nothing i can do.. I contacted hopone as i said, as far as they're concerned the problem is on my side, and my isp say they have no problems, so i'll just have to come on at certain times late at night and early in the morning when servers aren't busy - when my lag is usually lower (but still quite high) and low enough to play... I used to be on tw all the time now i probably won't get on much
[EDIT] oh i forgot i left ^^

[Fair]

Lag

Since moving to my new place i get intemittant lags sessions and get specced:

Tracing Zone: SSCU Trench Wars IP Address: 66.36.241.110

Hop IP Address Host Name Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
1 192.168.0.1 myrouter.home 0.0 0 0 0
2 87.87.254.201 cr7.thbz.uk.easynet.net 0.0 40 40 90
3 82.111.105.161 <unknown> 98.0 30 30 30
4 89.200.130.101 ip-89-200-130-101.ov.easynet.net 99.0 40 40 40
5 89.200.130.100 ip-89-200-130-100.ov.easynet.net 99.0 40 40 40
6 217.204.60.93 te0-0-0-1.gr10.bwnyc.us.easynet. 4.7 40 50 110
7 66.36.224.209 nyc1.ge11-2.core2.dca2.hopone.ne 99.0 900 900 900
8 66.36.224.228 vl2.msfc1.distb1.dca2.hopone.net 99.0 110 110 110
9 66.36.241.110 sls-cb9p7.dca2.superb.net 0.0 110 110 110

Cycles: 105

C:\Documents and Settings\Fairlights>ping -t 66.36.241.110

Pinging 66.36.241.110 with 32 bytes of data:

Reply from 66.36.241.110: bytes=32 time=115ms TTL=119
Reply from 66.36.241.110: bytes=32 time=115ms TTL=119
Reply from 66.36.241.110: bytes=32 time=116ms TTL=119
Reply from 66.36.241.110: bytes=32 time=115ms TTL=119
Reply from 66.36.241.110: bytes=32 time=116ms TTL=119
Reply from 66.36.241.110: bytes=32 time=116ms TTL=119
Reply from 66.36.241.110: bytes=32 time=117ms TTL=119
Reply from 66.36.241.110: bytes=32 time=116ms TTL=119
Reply from 66.36.241.110: bytes=32 time=116ms TTL=119
Reply from 66.36.241.110: bytes=32 time=115ms TTL=119


Ping statistics for 66.36.241.110:
Packets: Sent = 133, Received = 133, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 117ms, Average = 115ms




Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.home [192.168.0.1]
2 45 ms 44 ms 58 ms cr7.thbz.uk.easynet.net [87.87.254.201]
3 39 ms 40 ms 40 ms 82.111.105.161
4 43 ms 43 ms 43 ms ip-89-200-130-101.ov.easynet.net [89.200.130.101]
5 42 ms 42 ms 41 ms ip-89-200-130-100.ov.easynet.net [89.200.130.100]
6 111 ms 110 ms 110 ms te0-0-0-1.gr10.bwnyc.us.easynet.net [87.86.77.105]
7 933 ms * 905 ms nyc1.ge11-2.core2.dca2.hopone.net [66.36.224.209]
8 116 ms 116 ms 117 ms vl2.msfc1.distb1.dca2.hopone.net [66.36.224.228]
9 116 ms 117 ms 116 ms sls-cb9p7.dca2.superb.net [66.36.241.110]

Trace complete.

Got any ideas?