Using an alternate route to target address

simplefranco

Distinguished
Oct 9, 2010
54
0
18,630
Hello everyone, I have become aware of an issue while playing on-line games, mainly League of Legends. Server instability and higher than expected latency is known to players in this game, but I believe I have a different issue concerning how my machine connects to the server.

We are talking about the following address:
mx1.eu.lol.riotgames.com

I usually play with a friend and we have the same ISP. However, since we are from different towns, we connect to the server through different routes. Here's a dump of my friends tracert:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 12 ms 6 ms 7 ms bl3-72-153.dsl.telepac.pt [213.13.72.153]
4 10 ms 11 ms 11 ms dvs-cr1-hu-3-0-0.cprm.net [195.8.10.209]
5 55 ms 54 ms 51 ms lon1-cr1-be2.cprm.net [195.8.1.10]
6 52 ms 55 ms 55 ms lon3-cr1-be3.cprm.net [195.8.1.6]
7 52 ms 51 ms 73 ms ge-0.linx.london03.uk.bb.gin.ntt.net [195.66.224.138]
8 77 ms 79 ms 65 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.138]
9 86 ms 87 ms 85 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.54]
10 60 ms 64 ms 60 ms 212.119.15.6
11 58 ms 57 ms 59 ms border2.t7-1-bbnet1.fra002.pnap.net [95.172.67.2]
12 60 ms 58 ms 63 ms mx1.eu.lol.riotgames.com [95.172.65.1]

And here's mine:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 5 ms 1 ms 1 ms 192.168.1.254
3 * * * Request timed out.
4 13 ms 18 ms 12 ms bl3-74-177.dsl.telepac.pt [213.13.74.177]
5 9 ms 10 ms 11 ms bt-cr1-hu-3-0-0.cprm.net [195.8.10.213]
6 106 ms 102 ms 99 ms lon3-cr1-be2.cprm.net [195.8.0.242]
7 105 ms 100 ms 119 ms ge-0.linx.london03.uk.bb.gin.ntt.net [195.66.224.138]
8 * 62 ms * ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.138]
9 64 ms 60 ms 62 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.54]
10 117 ms 112 ms 114 ms 212.119.15.6
11 115 ms 114 ms 114 ms border2.t7-1-bbnet1.fra002.pnap.net [95.172.67.2]
12 115 ms 112 ms 117 ms mx1.eu.lol.riotgames.com [95.172.65.1]

I have highlighted the different routes we connect, and you can see they are different devices on the telepac.pt network. This leads me to believe that the machine my friend connects to, has a "smarter" route to the target.

This isn't permanent, but it feels like a cycle. Mostly noticeable on weekends and daylight time. It ends up being frustrating because I could get used to 110ms the same way I can get used to 60ms, but the shifting makes it impossible to get used to.

So to sum it up, my question would be as follows:
Is there any way I can setup a route to be the same as my friends to avoid this daylight latency shifting, considering I have "admin" access to my router? I say "admin" because I know the admin interface is limited, and I believe there are some things I may not be able to do.

Any advice appreciated. Thanks in advance :)
 
You have absolutely no control over anything once it leaves you house. Ignoring the stuff in the hops in the middle for now if the ping time to hop 12 is consistently 112 for you and consistently 60ms the it just means you have a longer path from your house to the server. It generally means that you are physically farther away but it can also be ISP pathing.

So from hop 7 on they are identical path so it is unlikely anything past here is the issue. What is really strange your friend has 1 more hop than you but a faster path. In any case the major difference appears to occur when the data is going to various routers, you can guess by the names, that reside in london. You would have to find out where the router in hop 4 of the first one is compared to hop 5 in the second one.

My "guess" is that there is some issue with the ISP CPRMNET which is based in portgal and ISP NTT at their peering points in london. Still even if you know this what can you do call up NTT or CPRMNET and tell them to fix it ? It would take you hours to just find a person who understands what you are talking about.

The really bad news is this trace only represents the for data coming to you not the other way around. this is why you see the strangeness on the ip 129.250.4.54. It is very likely the data is taking different paths going and coming from the location.
 

simplefranco

Distinguished
Oct 9, 2010
54
0
18,630


Hey bill thanks for your input. You confirmed what I already feared: I can't touch those routing tables... But your solution could work. I pinged my friends IP (supposedly - since we used whatsmyip, which is not always reliable) and I had an amazing 5ms response. So in theory I'd be getting those extra 5ms depending on his machine.

I do have some basics on networking but I've never setup a VPN but I'll have a look at it. I believe it can be done by software alone, right (and probably some port forwarding, but I'm just guessing) ?

Just out of curiosity, here's the tracert I did a couple of minutes ago:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 1 ms 1 ms 1 ms 192.168.1.254
3 * * * Request timed out.
4 12 ms 14 ms 15 ms bl3-74-177.dsl.telepac.pt [213.13.74.177]
5 11 ms 10 ms 11 ms bt-cr1-hu-3-0-0.cprm.net [195.8.10.213]
6 76 ms 70 ms 70 ms lon3-cr1-be2.cprm.net [195.8.0.242]
7 141 ms 73 ms 73 ms ge-0.linx.london03.uk.bb.gin.ntt.net [195.66.224.138]
8 70 ms 63 ms 67 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.138]
9 62 ms 60 ms 59 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.54]
10 67 ms 61 ms 66 ms 212.119.15.6
11 59 ms 60 ms 63 ms border2.po2-8g-bbnet2.fra002.pnap.net [95.172.67.66]
12 60 ms 60 ms 65 ms mx1.eu.lol.riotgames.com [95.172.65.1]

A pretty decent 60ms, like I said I'd have in a "normal day", ah.

Thanks again, cheers.