Gaming Zone > [MiA] Servers
Routing issues
Gil-galad:
I'm wondering about something about the results I had testing yesterday.
In game, I'm shown that I have no PL, but with the mtr command in the konsole, that's a completely different story (here a printscreen)
So I know it's my ISP's fault, and i'll perhaps go to another one soon, but anyway, why the discrepancy?
Nardaq_NL:
Pinging to the hops it self isn't reliable. This can if the hops next to it has the same or worse ping/packet loss.
General idea is to start with the end hop and work your way op to find the dodgy one.
A trace is only a single shot. Try use a ping-plotter similar program for linux to create a history of pings / packet loss / routes.
This will give you way better overview of your internet connection.
This is a plot on my end for example. As you can see hop 11 has always PL, but the end hop experiencing no issue.
and this is how it not suppose to look like. (virginmedia issue 1,5 month ago)
Gil-galad:
The MTR command does just that, afaik. It uses ICMP packets by default.
I've tried running it with UDP packets since ut2004 uses UDP, but the results are substantially worse, packet loss wise - and last hop, thus miasma server, doesn't respond. I'll try running it again after being routed through a new ISP.
Resike:
If you are bombarding addresses with frequent ping packets they gonna throw those away due to a more strict ddos protection, not because of actual packet loss.
Set yout ping interval to 10 seconds and there will be no ignored packets.
If you ping your own router fast enough you gonna see packet losses there too.
holyspam:
The last few days, the routing became different and my ping jumped from 26-27 to 34-37ms
Other people had a change in their total latency to the server as well.
Best example is kops who went from 8-12ms to 24+
The routing changes mid-testing and one results in 19 hops, one results in 21 hops
Either that, or there is a loop somewhere in the path.
Here's a UDP traceroute I did from my router.
--- Code: ---traceroute to 80.4.151.145, 25 hops max, 38 byte packets
1 10.10.10.1 (10.10.10.1) 1.155 ms 1.159 ms 1.769 ms
2 * * *
3 90-183-197-122.rcq.o2.cz (90.183.197.122) 1.967 ms 2.027 ms 1.980 ms
4 194.228.115.71 (194.228.115.71) 1.868 ms 1.458 ms 4.517 ms
5 90.182.79.201 (90.182.79.201) 1.538 ms 1.022 ms 1.170 ms
6 90.182.78.193 (90.182.78.193) 1.885 ms 1.926 ms 1.669 ms
7 194.228.115.65 (194.228.115.65) 1.827 ms 2.542 ms 1.891 ms
8 194.228.115.66 (194.228.115.66) 2.831 ms 2.091 ms 2.095 ms
9 * * *
10 hbg-bb3-link.ip.twelve99.net (62.115.124.26) 15.826 ms 15.553 ms 15.649 ms
11 ldn-bb1-link.ip.twelve99.net (80.91.249.10) 24.700 ms 24.897 ms de-fra02a-ri1-ae-7-0.aorta.net (213.46.177.137) 8.790 ms
12 de-fra02a-rc1-ae-30-0.aorta.net (84.116.137.18) 15.162 ms 15.907 ms ldn-b2-link.ip.twelve99.net (62.115.122.189) 25.233 ms
13 uk-lon03a-ri2-ae-20-0.aorta.net (213.46.174.117) 25.118 ms nl-ams02a-rc2-lag-8-0.aorta.net (84.116.130.98) 15.321 ms uk-lon03a-ri2-ae-20-0.aorta.net (213.46.174.117) 24.565 ms
14 nl-ams04a-ri3-ae-8-0.aorta.net (84.116.130.97) 15.005 ms * *
15 * * brnt-ic-3-ae0-0.network.virginmedia.net (62.253.174.114) 27.653 ms
16 * nrth-ic-3-ae0-0.network.virginmedia.net (62.253.174.78) 22.849 ms *
17 * cdif-core-2b-ae2-0.network.virginmedia.net (62.254.84.122) 28.720 ms brnt-ic-3-ae0-0.network.virginmedia.net (62.253.174.114) 25.718 ms
18 * cdif-metnet-2b-lag-55.network.virginmedia.net (86.28.69.6) 28.407 ms *
19 drkn-bh1-ib1.network.virginmedia.net (213.104.164.218) 34.686 ms 34.699 ms 34.153 ms
20 * cdif-metnet-2b-lag-56.network.virginmedia.net (62.252.32.70) 26.370 ms 26.480 ms
21 * * drkn-bh1-ib1.network.virginmedia.net (213.104.164.218) 34.527 ms
22 * * *
23 * * *
24 * * *
25 * * *
Trace Complete.
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version