Routing issues (Read 52781 times)

zeus · « **on:** August 07, 2022, 21:28 »

Routing issues INSIDE London (I assume the rest with PL / high ping have it similar), target is 80.4.151.145

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 
| 
| 
|             rom-b2-link.ip.twelve99.net -    0 |  200 |  200 |   20 |   21 |   29 |   22 |
|            hbg-bb4-link.ip.twelve99.net -    0 |  200 |  200 |   34 |   35 |   53 |   36 |
|            ldn-bb4-link.ip.twelve99.net -    1 |  197 |  196 |    0 |   52 |   80 |   53 |
|             ldn-b3-link.ip.twelve99.net -    0 |  200 |  200 |   46 |   46 |   53 |   47 |
|upc-ic306717-ldn-b3.ip.twelve99-cust.net -    0 |  200 |  200 |   45 |   46 |   66 |   46 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|          uk-lon03a-ri2-ae-5-0.aorta.net -    0 |  200 |  200 |   46 |   46 |   86 |   46 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|sotn-core-2b-ae2-0.network.virginmedia.net -    3 |  185 |  181 |   82 |   94 |  134 |   99 |
|sotn-metnet-3a-lag-56.network.virginmedia.net -   24 |  105 |   80 |    0 |   95 |  103 |   93 |
|    drkn-bh1-ia1.network.virginmedia.net -    2 |  192 |  190 |   85 |   96 |  103 |  101 |
|                            miasma.rocks -    2 |  193 |  191 |   84 |   96 |  103 |  101 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL

Problematic is the unknown provider (aorta seems like some central backone) -> virgin routing which
a) introduces +50ms in ping
b) 2-3% constant PL

EDIT: seems like WinMTR has trouble reverse lookuping the IPs - there is NO WAY that the routing goes with 20ms to Rome - that host should be "war-b2-link.telia.net [62.115.179.208]"

vkn · « **Reply #1 on:** August 07, 2022, 21:33 »

Can confirm...

16 41 ms 41 ms 41 ms uk-lon03a-ri2-ae-2-0.aorta.net [84.116.135.46]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 87 ms 97 ms 85 ms sotn-core-2b-ae2-0.network.virginmedia.net [62.254.85.142]
21 * * * Request timed out.
22 89 ms 88 ms 82 ms drkn-bh1-ia1.network.virginmedia.net [213.48.17.22]
23 95 ms 89 ms 86 ms miasma.rocks [80.4.151.145]

DNT.GR · « **Reply #2 on:** August 07, 2022, 21:56 »

My info also.

DNT.GR · « **Reply #3 on:** August 08, 2022, 08:48 »

https://www.ispreview.co.uk/index.php/2022/04/peak-time-latency-strikes-part-of-virgin-medias-uk-network.html
https://community.virginmedia.com/t5/Networking-and-WiFi/VM-CORE-NETWORK-FAILURE-URGANT/td-p/4986440/highlight/false

hagis · « **Reply #4 on:** August 08, 2022, 09:04 »

Quote from: zeus on August 07, 2022, 21:28

Routing issues INSIDE London (I assume the rest with PL / high ping have it similar), target is 80.4.151.145

Code: [Select]
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | | | | rom-b2-link.ip.twelve99.net - 0 | 200 | 200 | 20 | 21 | 29 | 22 | | hbg-bb4-link.ip.twelve99.net - 0 | 200 | 200 | 34 | 35 | 53 | 36 | | ldn-bb4-link.ip.twelve99.net - 1 | 197 | 196 | 0 | 52 | 80 | 53 | | ldn-b3-link.ip.twelve99.net - 0 | 200 | 200 | 46 | 46 | 53 | 47 | |upc-ic306717-ldn-b3.ip.twelve99-cust.net - 0 | 200 | 200 | 45 | 46 | 66 | 46 | | No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 | | uk-lon03a-ri2-ae-5-0.aorta.net - 0 | 200 | 200 | 46 | 46 | 86 | 46 | | No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 | |sotn-core-2b-ae2-0.network.virginmedia.net - 3 | 185 | 181 | 82 | 94 | 134 | 99 | |sotn-metnet-3a-lag-56.network.virginmedia.net - 24 | 105 | 80 | 0 | 95 | 103 | 93 | | drkn-bh1-ia1.network.virginmedia.net - 2 | 192 | 190 | 85 | 96 | 103 | 101 | | miasma.rocks - 2 | 193 | 191 | 84 | 96 | 103 | 101 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL

Problematic is the unknown provider (aorta seems like some central backone) -> virgin routing which
a) introduces +50ms in ping
b) 2-3% constant PL

EDIT: seems like WinMTR has trouble reverse lookuping the IPs - there is NO WAY that the routing goes with 20ms to Rome - that host should be "war-b2-link.telia.net [62.115.179.208]"

ah,. I am definitely seeing ping spikes these last few days,. my ping was previously 24ms - now it's generally double that and then it gets upset and goes much worse

Code: [Select]

  3    11 ms    11 ms    11 ms  63.130.104.202
  4    12 ms    10 ms    10 ms  ae5-100-xcr1.man.cw.net [195.89.96.113]
  5    16 ms    16 ms    15 ms  ae21-xcr1.ltw.cw.net [195.2.9.97]
  6    18 ms    16 ms    16 ms  uk-lon03a-ri2-ae-10-0.aorta.net [213.46.174.129]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    46 ms    46 ms    46 ms  sotn-core-2b-ae2-0.network.virginmedia.net [62.254.85.142]
 11    46 ms    46 ms    47 ms  sotn-metnet-3a-lag-56.network.virginmedia.net [86.28.60.202]
 12    47 ms    47 ms    47 ms  drkn-bh1-ia1.network.virginmedia.net [213.48.17.22]
 13    48 ms    48 ms    48 ms  miasma.rocks [80.4.151.145]

kops · « **Reply #5 on:** August 08, 2022, 11:37 »

Tracing route to miasma.rocks [80.4.151.145]
over a maximum of 30 hops:

1 1 ms 269 ms 1 ms 192.168.1.254 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 102 ms 12 ms 67 ms be3671.ccr51.lhr01.atlas.cogentco.com [130.117.48.137]
5 62 ms 101 ms 101 ms be3487.ccr41.lon13.atlas.cogentco.com [154.54.60.5]
6 34 ms 69 ms 101 ms be2868.ccr21.lon01.atlas.cogentco.com [154.54.57.154]
7 13 ms 16 ms 13 ms uk-lon01b-ri1-ae-3-0.aorta.net [213.46.174.45]
8 * * * Request timed out.
9 13 ms 14 ms 51 ms uk-lon03a-ri2-ae-5-0.aorta.net [84.116.135.42]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 82 ms 47 ms 52 ms sotn-core-2b-ae2-0.network.virginmedia.net [62.254.85.142]
14 45 ms 54 ms 49 ms sotn-metnet-3a-lag-56.network.virginmedia.net [86.28.60.202]
15 62 ms 59 ms 55 ms drkn-bh1-ia1.network.virginmedia.net [213.48.17.22]
16 58 ms 56 ms 57 ms miasma.rocks [80.4.151.145]

holyspam · « **Reply #6 on:** August 08, 2022, 13:39 »

Please make sure you are using the gameserver IP (80.4.151.145), not the website.

kops · « **Reply #7 on:** August 08, 2022, 14:03 »

delete.

Piglet · « **Reply #8 on:** August 08, 2022, 20:26 »

Quote from: holyspam on August 08, 2022, 13:39

Please make sure you are using the gameserver IP (80.4.151.145), not the website.

It should be the same apart from the internal datacentre routing.

If possible, I'd use linux "traceroute", as that uses UDP packets like the game, rather than TCP packets which is what windows tracert uses by default.

Miauz55555 · « **Reply #9 on:** August 08, 2022, 22:30 »

Code: [Select]

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                                   -    0 |  104 |  104 |    1 |    1 |    3 |    1 |
|                                                  -    0 |  104 |  104 |    2 |    3 |   19 |    2 |
|                                                  -    0 |  104 |  104 |    2 |    5 |   70 |    3 |
|             hbg-b1-link.ip.twelve99.net -    0 |  104 |  104 |    5 |    6 |   28 |    6 |
|            hbg-bb3-link.ip.twelve99.net -    0 |  104 |  104 |    5 |    6 |   19 |    6 |
|            ldn-bb1-link.ip.twelve99.net -   12 |   68 |   60 |   18 |   18 |   23 |   18 |
|             ldn-b2-link.ip.twelve99.net -    0 |  104 |  104 |   18 |   18 |   23 |   18 |
|         uk-lon03a-ri2-ae-20-0.aorta.net -    5 |   89 |   85 |   18 |   18 |   35 |   18 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|sotn-core-2b-ae2-0.network.virginmedia.net -    3 |   96 |   94 |   65 |   72 |   89 |   85 |
|sotn-metnet-3a-lag-56.network.virginmedia.net -   87 |   23 |    3 |    0 |   73 |   75 |   72 |
|    drkn-bh1-ia1.network.virginmedia.net -    4 |   92 |   89 |   65 |   72 |   81 |   72 |
|                            miasma.rocks -    3 |   96 |   94 |   62 |   71 |   79 |   73 |
|________________________________________________|______|______|______|______|______|______|

zeus · « **Reply #10 on:** August 08, 2022, 22:31 »

It does not really matter which OS you use to run it from - the routing is identical. Run from a Debian in München

Code: [Select]

traceroute to 80.4.151.145 (80.4.151.145), 30 hops max, 60 byte packets
 1  
 2  
 3  mcn-b3-link.ip.twelve99.net (62.115.120.79)  0.856 ms  0.823 ms  0.827 ms
 4  ffm-bb2-link.ip.twelve99.net (62.115.124.46)  6.207 ms  6.229 ms  6.168 ms
 5  prs-bb2-link.ip.twelve99.net (62.115.114.98)  15.671 ms prs-bb2-link.ip.twelve99.net (62.115.122.138)  15.667 ms prs-bb2-link.ip.twelve99.net (62.115.114.98)  15.749 ms
 6  ldn-bb4-link.ip.twelve99.net (62.115.133.238)  21.712 ms  21.937 ms  21.876 ms
 7  ldn-b2-link.ip.twelve99.net (62.115.120.239)  21.271 ms  21.506 ms ldn-b3-link.ip.twelve99.net (62.115.122.181)  21.925 ms
 8  uk-lon03a-ri2-ae-20-0.aorta.net (213.46.174.117)  21.769 ms  21.770 ms upc-ic306717-ldn-b3.ip.twelve99-cust.net (213.248.84.26)  21.146 ms
 9  * * *
10  * uk-lon03a-ri2-ae-5-0.aorta.net (84.116.135.42)  25.537 ms *
11  * * *
12  * sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  78.214 ms *
13  * * *
14  sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  69.153 ms  75.465 ms  65.761 ms

My theory (currently) based on map change event randomly resetting the pings exactly for 1 MAP (!) is that it has to be some anti-DDOS type of firewall -> the small continuous packets are considered DDOS -> the firewall introduces PL and high ping (either on purpose or as per link - since it is just shit slow) to save the target from having to serve all the requests
Now when typing this & Googling then something from https://subspacepowered.medium.com/how-to-implement-ddos-attack-prevention-mitigation-without-jeopardizing-latency-e8bcdd70a57 sounds similar ->

Code: [Select]

Traditional Security Companies Incur Latency Through Proxying
Current providers regularly rely on proxying traffic as the primary tool for DDoS mitigation. Proxying involves taking the data through a scrubbing server that forwards traffic and runs analysis before sending it back to the user.

Moving data through a proxy for scrubbing increases ping time and latency, resulting in additional lag. It’s only a good solution for web traffic that doesn’t require real-time communications.

The theory is based only on ingame observations by me & Nyrde - when a small disconnect (read: map change) occurs, the ping & PL is fixed (or semi-fixed) exactly for the duration of the next small disconnect (read: another map change). So the theory is ... exactly what it is - a theory
Feel free to comment

EDIT: why would it detect UDP packets as DDOS - because as Pig said "Linux uses UDP to ping" -> for whatever firewall it will not be able to differentiate whether it is a ping attack with huge packets or gaming

Gil-galad · « **Reply #11 on:** August 09, 2022, 16:37 »

If usefull, here is what I get from traceroute (9th of august) :

Code: [Select]

traceroute 80.4.151.145                                                                                                                                            ✔  22s  
traceroute to 80.4.151.145 (80.4.151.145), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.657 ms  0.799 ms  0.636 ms
 2  2.96.54.77.rev.vodafone.pt (77.54.96.2)  11.888 ms  12.024 ms  13.025 ms
 3  24.50.174.83.rev.vodafone.pt (83.174.50.24)  14.213 ms  14.354 ms  13.042 ms
 4  ae5-100-ucr1.lis.cw.net (195.10.57.9)  20.073 ms  18.755 ms  20.061 ms
 5  ae21-xcr1.max.cw.net (195.2.24.233)  52.895 ms  52.299 ms  51.771 ms
 6  ae25-xcr3.prp.cw.net (195.2.8.137)  46.045 ms  44.753 ms  44.746 ms
 7  ae3-xcr1.bud.cw.net (195.2.28.89)  65.711 ms  50.719 ms  49.615 ms
 8  uk-lon03a-ri2-ae-10-0.aorta.net (213.46.174.129)  65.746 ms  65.740 ms  65.735 ms
 9  * * *
10  * * *
11  * * *
12  sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  99.229 ms  93.365 ms  94.808 ms
13  * * *
14  drkn-bh1-ia1.network.virginmedia.net (213.48.17.22)  94.806 ms  105.863 ms  95.691 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

EDIT : Now without the vpn
EDIT 1 : I tried again today (10th of august), and here is the result :

Code: [Select]

traceroute 80.4.151.145                                                                                                                                            ✔  18s  
traceroute to 80.4.151.145 (80.4.151.145), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.648 ms  0.631 ms  0.789 ms
 2  * * *
 3  24.50.174.83.rev.vodafone.pt (83.174.50.24)  13.700 ms  14.255 ms  14.249 ms
 4  ae5-100-ucr1.lis.cw.net (195.10.57.9)  18.950 ms  19.200 ms  19.193 ms
 5  ae21-xcr1.max.cw.net (195.2.24.233)  60.185 ms  53.409 ms  53.404 ms
 6  ae25-xcr3.prp.cw.net (195.2.8.137)  44.894 ms  43.761 ms  44.745 ms
 7  ae29-xcr1.ltw.cw.net (195.2.28.89)  51.236 ms  49.219 ms  49.446 ms
 8  uk-lon03a-ri2-ae-10-0.aorta.net (213.46.174.129)  51.280 ms  50.912 ms  50.661 ms
 9  * * *
10  * * *
11  * * *
12  sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  104.397 ms  102.737 ms  104.048 ms
13  sotn-metnet-3a-lag-56.network.virginmedia.net (86.28.60.202)  104.386 ms  81.139 ms  105.270 ms
14  drkn-bh1-ia1.network.virginmedia.net (213.48.17.22)  105.550 ms  103.080 ms  106.372 ms

Miauz55555 · « **Reply #12 on:** August 09, 2022, 23:06 »

Played today .. had ~ 80 to 130 ping and ~6 to ~20% PL. Was like on a US server with PL. =D
Blub seems to have a stable connection, probably other routing than.

Code: [Select]

tracert 80.4.151.145
  1
  2
  3
  4     8 ms     5 ms     5 ms  hbg-b1-link.ip.twelve99.net [213.248.92.214]
  5     7 ms     6 ms     7 ms  hbg-bb3-link.ip.twelve99.net [213.155.135.80]
  6    19 ms    18 ms    18 ms  ldn-bb1-link.ip.twelve99.net [80.91.249.10]
  7    19 ms    42 ms    18 ms  ldn-b2-link.ip.twelve99.net [62.115.122.189]
  8    19 ms    18 ms    18 ms  uk-lon03a-ri2-ae-20-0.aorta.net [213.46.174.117]
  9     *        *        *     Zeitüberschreitung der Anforderung.
 10    89 ms     *       85 ms  brnt-ic-1-ae0-0.network.virginmedia.net [62.254.42.198]
 11     *        *        *     Zeitüberschreitung der Anforderung.
 12    75 ms    75 ms    72 ms  sotn-core-2b-ae2-0.network.virginmedia.net [62.254.85.142]
 13    74 ms    72 ms    72 ms  sotn-metnet-3a-lag-56.network.virginmedia.net [86.28.60.202]
 14    75 ms    75 ms    75 ms  drkn-bh1-ia1.network.virginmedia.net [213.48.17.22]
 15    77 ms    75 ms    72 ms  miasma.rocks [80.4.151.145]

hagis · « **Reply #13 on:** August 10, 2022, 20:02 »

Code: [Select]

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %loss  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  archer -    0 |  143 |  143 |    0 |    0 |    5 |    0 |
|                             84.65.128.1 -    0 |  143 |  143 |    9 |    9 |   11 |    9 |
|                          63.130.104.202 -    0 |  143 |  143 |    9 |   10 |   17 |    9 |
|                 ae5-100-xcr1.man.cw.net -    0 |  142 |  142 |    9 |   10 |   27 |   14 |
|                    ae21-xcr1.ltw.cw.net -    0 |  143 |  143 |   15 |   17 |   54 |   17 |
|         uk-lon03a-ri2-ae-10-0.aorta.net -    0 |  142 |  142 |   15 |   17 |   39 |   17 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|sotn-core-2b-ae2-0.network.virginmedia.net -    0 |  143 |  143 |   45 |   47 |   74 |   46 |
|sotn-metnet-3a-lag-56.network.virginmedia.net -   62 |   75 |   29 |   45 |   46 |   47 |   46 |
|    drkn-bh1-ia1.network.virginmedia.net -    0 |  143 |  143 |   46 |   47 |   60 |   47 |
|                            miasma.rocks -    0 |  143 |  143 |   46 |   47 |   67 |   47 |
|________________________________________________|______|______|______|______|______|______|

am getting packet loss and not good ping,. is unplayable really,. worse than playing on a US server (much worse)

not sure what to do - other than not play,. not everyone is seeing same issue at same time so it's strange one?

zeus · « **Reply #14 on:** August 10, 2022, 22:34 »

Something to consider - UDP routing from Düsseldorf to a slightly different IP

Code: [Select]

traceroute to 80.4.151.146 (80.4.151.146), 30 hops max, 60 byte packets

 2  et-4-0-8.edge6.Dusseldorf1.Level3.net (62.67.22.193)  7.057 ms  7.031 ms ddf-b2-link.ip.twelve99.net (62.115.171.184)  6.780 ms
 3  adm-bb4-link.ip.twelve99.net (62.115.135.146)  16.285 ms  16.252 ms  16.226 ms
 4  uk-lon01c-ri2-ae-22-0.aorta.net (213.46.175.97)  16.580 ms ldn-bb4-link.ip.twelve99.net (62.115.134.27)  16.163 ms telw-ic-5-ae19-0.network.virginmedia.net (213.105.23.0)  17.384 ms
 5  ldn-b2-link.ip.twelve99.net (62.115.120.239)  15.654 ms  15.452 ms *
 6  sotn-core-2a-ae2-0.network.virginmedia.net (62.254.85.138)  20.046 ms uk-lon03a-ri2-ae-20-0.aorta.net (213.46.174.117)  12.457 ms  14.782 ms
 7  * * sotn-metnet-3a-lag-55.network.virginmedia.net (86.28.60.194)  16.014 ms
 8  * drkn-bh1-ia1.network.virginmedia.net (213.48.17.22)  20.884 ms uk-lon03a-ri2-ae-2-0.aorta.net (84.116.135.46)  10.837 ms
 9  * * unreal.miasma.rocks (80.4.151.146)  23.640 ms

Maybe switching the IPs would fix the problems temporarily?

Routing issues (Read 52781 times)

zeus

Routing issues

vkn

Re: Routing issues

DNT.GR

Re: Routing issues

DNT.GR

Re: Routing issues

hagis

Re: Routing issues

kops

Re: Routing issues

holyspam

Re: Routing issues

kops

Re: Routing issues

Piglet

Re: Routing issues

Miauz55555

Re: Routing issues

zeus

Re: Routing issues

Gil-galad

Re: Routing issues

Miauz55555

Re: Routing issues

hagis

Re: Routing issues

zeus

Re: Routing issues