Miasma Community

Gaming Zone => [MiA] Servers => Topic started by: zeus on August 07, 2022, 21:28

Title: Routing issues
Post by: 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]"
Title: Re: Routing issues
Post by: vkn 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]
Title: Re: Routing issues
Post by: DNT.GR on August 07, 2022, 21:56
My info also.
Title: Re: Routing issues
Post by: DNT.GR 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
Title: Re: Routing issues
Post by: hagis 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


|------------------------------------------------------------------------------------------|
|                                      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


  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]

Title: Re: Routing issues
Post by: kops 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]

Title: Re: Routing issues
Post by: holyspam on August 08, 2022, 13:39
Please make sure you are using the gameserver IP (80.4.151.145), not the website.
Title: Re: Routing issues
Post by: kops on August 08, 2022, 14:03
delete.
Title: Re: Routing issues
Post by: Piglet 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.
Title: Re: Routing issues
Post by: Miauz55555 on August 08, 2022, 22:30
|------------------------------------------------------------------------------------------|
|                                      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 |
|________________________________________________|______|______|______|______|______|______|
   
Title: Re: Routing issues
Post by: zeus 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

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 ->

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
Title: Re: Routing issues
Post by: Gil-galad on August 09, 2022, 16:37
If usefull, here is what I get from traceroute (9th of august) :

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 :

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
Title: Re: Routing issues
Post by: Miauz55555 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.
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]
Title: Re: Routing issues
Post by: hagis on August 10, 2022, 20:02
|------------------------------------------------------------------------------------------|
|                                      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?
Title: Re: Routing issues
Post by: zeus on August 10, 2022, 22:34
Something to consider - UDP routing from Düsseldorf to a slightly different IP

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?
Title: Re: Routing issues
Post by: Miauz55555 on August 11, 2022, 07:21
Funny is, that when you route from DE over NL into UK you get anouther routing and have no problem. If you route direct from DE to UK the chance is high you get the problems in the UK.

My connection goes into UK on the first hop with 18 ms .. the next has the problem.

@hagis when you have problems also when you are in UK can you try a IP in DE?
That's the ceonss .. it's sitting next to the backbone in Frankfurt.
tracert 176.57.141.10

Routenverfolgung zu 176.57.141.10 über maximal 30 Hops

  1     1 ms     1 ms     1 ms 
  2     3 ms     1 ms     1 ms 
  3     3 ms     2 ms     2 ms 
  4     6 ms     5 ms     5 ms  hbg-b1-link.ip.twelve99.net [213.248.92.214]
  5     7 ms     6 ms     5 ms  hbg-bb4-link.ip.twelve99.net [213.155.135.84]
  6    15 ms    14 ms    14 ms  ffm-bb2-link.ip.twelve99.net [62.115.138.172]
  7    14 ms    13 ms    13 ms  ffm-b5-link.ip.twelve99.net [62.115.114.91]
  8    13 ms    12 ms    11 ms  ae10-0.fra10.core-backbone.com [62.115.9.226]
  9    12 ms    12 ms    11 ms  cbb.fra14.edge-1.et-0-0-1 [5.56.21.154]
10    13 ms    11 ms    12 ms  core01.fra.ix.fra14.ae2.0 [94.250.214.1]
11    13 ms    12 ms    12 ms  spine1.fra.iw.xe-0-0-30.0 [94.250.214.251]
12    13 ms    11 ms    11 ms  176.57.141.10
Title: Re: Routing issues
Post by: hagis on August 11, 2022, 20:05
Quote from: zeus on August 10, 2022, 22:34
Something to consider - UDP routing from Düsseldorf to a slightly different IP

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?

humm,.

145 I get avg ping 47 at server
146 I get avg ping 67 at server
Title: Re: Routing issues
Post by: hagis on August 11, 2022, 20:08
Quote from: Miauz55555 on August 11, 2022, 07:21


@hagis when you have problems also when you are in UK can you try a IP in DE?
That's the ceonss .. it's sitting next to the backbone in Frankfurt.


we might need to conclude my ISP is crap...


|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  archer -    0 |   42 |   42 |    0 |    0 |    1 |    0 |
|                             84.65.128.1 -    6 |   39 |   37 |    9 |   10 |   17 |   10 |
|                          63.130.105.134 -    6 |   39 |   37 |   15 |   17 |   32 |   16 |
|           ae1-0.lon10.core-backbone.com -    3 |   40 |   39 |   17 |   18 |   27 |   18 |
|       ae16-2074.fra10.core-backbone.com -    6 |   39 |   37 |    0 |   27 |   30 |   28 |
|               cbb.fra14.edge-1.et-0-0-1 -    6 |   39 |   37 |    0 |   29 |   70 |   27 |
|               core01.fra.ix.fra14.ae2.0 -    6 |   39 |   37 |    0 |   30 |   87 |   53 |
|               spine2.fra.iw.xe-0-0-30.0 -    6 |   39 |   37 |    0 |   28 |   45 |   28 |
|                           176.57.141.10 -    6 |   39 |   37 |    0 |   27 |   31 |   27 |
|________________________________________________|______|______|______|______|______|______|
Title: Re: Routing issues
Post by: Stealer on August 11, 2022, 20:21
Hagis dude, looks like an internal issue, are you on adsl or fiber?
Title: Re: Routing issues
Post by: hagis on August 11, 2022, 21:05
is fibre to the premises
Title: Re: Routing issues
Post by: Stealer on August 11, 2022, 21:51
Probably not something I can help with, you shouldn't be getting pl on a fibre connection; it means your network is compromised (light getting in where it shouldn't).
Equally could be a nasty virus, run a scan anyway :) Eat cookies  8)
Title: Re: Routing issues
Post by: hagis on August 12, 2022, 12:58
it's an ISP / interconnect issue,.

typically I called ISP to complain and it's working ok now when I test it - lol

hopefully it was an issue that's fixed but probably not going to know until peak times in the evening...


|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  archer -    0 |  100 |  100 |    0 |    0 |   10 |    0 |
|                             84.65.128.1 -    2 |   99 |   98 |    9 |   13 |  170 |   10 |
|                          63.130.104.202 -    0 |  100 |  100 |    9 |   10 |   21 |   10 |
|                 ae5-100-xcr1.man.cw.net -    0 |  100 |  100 |    9 |   10 |   21 |   10 |
|                    ae21-xcr1.ltw.cw.net -    0 |  100 |  100 |   15 |   16 |   27 |   18 |
|         uk-lon03a-ri2-ae-10-0.aorta.net -    0 |  100 |  100 |   15 |   18 |   42 |   17 |
|                   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 -    0 |  100 |  100 |   17 |   20 |   59 |   20 |
|sotn-metnet-3a-lag-56.network.virginmedia.net -    0 |  100 |  100 |   18 |   18 |   35 |   18 |
|    drkn-bh1-ia1.network.virginmedia.net -    0 |  100 |  100 |   19 |   20 |   35 |   20 |
|                            miasma.rocks -    0 |  100 |  100 |   19 |   20 |   35 |   20 |
|________________________________________________|______|______|______|______|______|______|
Title: Re: Routing issues
Post by: Piglet on August 12, 2022, 20:03
I wouldn't expect pl on the second hop. Is that consistent over time? To other places? That's not acceptable from your ISP
Title: Re: Routing issues
Post by: holyspam on August 12, 2022, 20:59
Looks like *today* the issue is gone
Title: Re: Routing issues
Post by: hagis on August 12, 2022, 22:26
Quote from: Piglet on August 12, 2022, 20:03
I wouldn't expect pl on the second hop. Is that consistent over time? To other places? That's not acceptable from your ISP

yeah when I called them they took more interest than I expected and said it if happens again they will investigate further

Quote from: holyspam on August 12, 2022, 20:59
Looks like *today* the issue is gone

yep, has been good all day,. perhaps transient issue now resolved
Title: Re: Routing issues
Post by: Stealer on August 13, 2022, 17:35
Depending who you are with Hagis, I have access to most line tests etc for several isps :)
Title: Re: Routing issues
Post by: Gil-galad on August 14, 2022, 15:53
Hello,
This afternoon (14th of august), I had no pl, and my usual (normal) ping. I ran the traceroute command again :

traceroute to 80.4.151.145 (80.4.151.145), 30 hops max, 60 byte packets
1  _gateway (192.168.1.1)  0.854 ms  0.977 ms  1.097 ms
2  * * *
3  24.50.174.83.rev.vodafone.pt (83.174.50.24)  14.512 ms  14.981 ms  14.980 ms
4  ae5-100.ucr1.lis.cw.net (195.10.57.9)  22.104 ms  22.102 ms  22.101 ms
5  ae45-xcr1.max.cw.net (195.2.31.142)  49.993 ms  49.992 ms  50.282 ms
6  ae25-xcr3.prp.cw.net (195.2.8.137)  44.030 ms  42.705 ms  42.696 ms
7  ae15-xcr1.ltw.cw.net (195.2.8.225)  49.481 ms  46.544 ms  46.631 ms
8  uk-lon03a-ri2-ae-10-0.aorta.net (213.46.174.129)  48.616 ms  48.508 ms  48.660 ms
9  * * *
10  brnt-ic-1-ae0-0.network.virginmedia.net (62.254.42.198)  48.400 ms  47.030 ms  47.611 ms
11  * * *
12  sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  49.862 ms  49.217 ms  49.183 ms
13  sotn-metnet-3a-lag-56.network.virginmedia.net (86.28.60.202)  49.188 ms  49.444 ms  49.170 ms
14  drkn-bh1-ia1.network.virginmedia.net (213.48.17.22)  50.171 ms  50.662 ms  50.403 ms
15  miasma.rocks (80.4.151.145)  50.445 ms  50.635 ms  50.508 ms


EDIT : now redone with -I @Adler
Title: Re: Routing issues
Post by: -Adler- on August 14, 2022, 16:10
Quote from: Gil-galad on August 14, 2022, 15:53
Hello,
This afternoon (14th of august), I had no pl, and my usual (normal) ping. I ran the traceroute command again :

traceroute 80.4.151.145                                                                                                                                                    ✔
traceroute to 80.4.151.145 (80.4.151.145), 30 hops max, 60 byte packets
1  _gateway (192.168.1.1)  0.520 ms  0.695 ms  0.852 ms
2  2.96.54.77.rev.vodafone.pt (77.54.96.2)  12.665 ms  13.038 ms  11.958 ms
3  24.50.174.83.rev.vodafone.pt (83.174.50.24)  82.236 ms  82.230 ms  82.222 ms
4  ae5-100-ucr1.lis.cw.net (195.10.57.9)  19.012 ms  19.590 ms  17.325 ms
5  ae45-xcr1.max.cw.net (195.2.31.142)  49.204 ms  50.060 ms  50.053 ms
6  ae25-xcr3.prp.cw.net (195.2.8.137)  42.467 ms  43.355 ms  41.616 ms
7  ae3-xcr1.bud.cw.net (195.2.28.89)  48.846 ms  61.563 ms  56.526 ms
8  uk-lon03a-ri2-ae-10-0.aorta.net (213.46.174.129)  54.292 ms  54.157 ms  54.149 ms
9  * * *
10  * * *
11  * * *
12  sotn-core-2b-ae2-0.network.virginmedia.net (62.254.85.142)  51.085 ms  51.073 ms  52.044 ms
13  sotn-metnet-3a-lag-56.network.virginmedia.net (86.28.60.202)  50.919 ms  51.109 ms  49.537 ms
14  drkn-bh1-ia1.network.virginmedia.net (213.48.17.22)  52.500 ms  50.544 ms  52.957 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


use
traceroute -I 80.4.151.145
Title: Re: Routing issues
Post by: holyspam on August 14, 2022, 16:19
-U flag is more appropriate in this case
Unfortunately not available natively on windows
Title: Re: Routing issues
Post by: -Adler- on August 14, 2022, 17:07
Quote from: holyspam on August 14, 2022, 16:19
-U flag is more appropriate in this case
Unfortunately not available natively on windows
traceroute on linux use UDP default.
Title: Re: Routing issues
Post by: hagis on September 24, 2022, 21:17

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  archer -    0 |   14 |   14 |    0 |    0 |    1 |    0 |
|                            90.247.192.1 -    8 |   14 |   13 |    5 |    6 |   12 |    6 |
|                          63.130.127.221 -    8 |   13 |   12 |    6 |    7 |   11 |    8 |
|                ae15-100-xcr1.slo.cw.net -   25 |   12 |    9 |    7 |    7 |   12 |    8 |
|                     ae4-xcr1.ltw.cw.net -   16 |   13 |   11 |    8 |    9 |   15 |    9 |
|         uk-lon03a-ri2-ae-10-0.aorta.net -   25 |   12 |    9 |    8 |    9 |   18 |   18 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|tn-core-2b-ae2-0.network.virginmedia.net -   25 |   12 |    9 |    0 |   12 |   13 |   12 |
|metnet-3a-lag-56.network.virginmedia.net -   25 |   12 |    9 |   11 |   11 |   12 |   11 |
|    drkn-bh1-ia1.network.virginmedia.net -   17 |   12 |   10 |   12 |   12 |   13 |   12 |
|                     unreal.miasma.rocks -   25 |   12 |    9 |   12 |   12 |   14 |   13 |
|________________________________________________|______|______|______|______|______|______|


the good news is it looks like they changed the routing to the server (YaY) the bad news is huge and unplayable packet loss,. hopefully they will resolve(!)


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

  1     1 ms    <1 ms    <1 ms  archer [172.25.22.201]
  2     6 ms     6 ms     6 ms  90.247.192.1
  3     8 ms     7 ms     7 ms  63.130.127.221
  4     *        *        *     Request timed out.
  5     *       13 ms    14 ms  ae4-xcr1.ltw.cw.net [195.2.24.34]
  6    11 ms    11 ms    10 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    12 ms    12 ms    12 ms  sotn-core-2b-ae2-0.network.virginmedia.net [62.254.85.142]
11    17 ms    12 ms    14 ms  sotn-metnet-3a-lag-56.network.virginmedia.net [86.28.60.202]
12    13 ms    13 ms    12 ms  drkn-bh1-ia1.network.virginmedia.net [213.48.17.22]
13    13 ms    13 ms    14 ms  unreal.miasma.rocks [80.4.151.146]
Title: Re: Routing issues
Post by: Piglet on September 24, 2022, 22:21
Complain!
Title: Re: Routing issues
Post by: hagis on September 25, 2022, 21:42
Quote from: Piglet on September 24, 2022, 22:21
Complain!

yeah - haven't been in today but just looked and it's still messed up

will call them tomorrow - is not just mia,. even running a speedtest the download speed sucks
Title: Re: Routing issues
Post by: holyspam on September 25, 2022, 21:46
That looks local exchange, first hop has p/l too....bad config?
Title: Re: Routing issues
Post by: hagis on September 26, 2022, 09:32
nice,. looks like the ISP's monday crew fixed it and ping is pretty good :)


|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  archer -    0 |   19 |   19 |    0 |    0 |    1 |    0 |
|                            90.247.192.1 -    6 |   18 |   17 |    4 |    5 |   12 |    6 |
|                          63.130.127.221 -    0 |   19 |   19 |    6 |    7 |   13 |    7 |
|                ae15-100-xcr1.slo.cw.net -    0 |   19 |   19 |    7 |   10 |   49 |    7 |
|                     ae4-xcr1.ltw.cw.net -    0 |   19 |   19 |    8 |   10 |   21 |   12 |
|         uk-lon03a-ri2-ae-10-0.aorta.net -    0 |   19 |   19 |    8 |    9 |   18 |    9 |
|                   No response from host -  100 |   11 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   11 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   11 |    0 |    0 |    0 |    0 |    0 |
|tn-core-2b-ae2-0.network.virginmedia.net -    0 |   19 |   19 |   10 |   12 |   26 |   12 |
|metnet-3a-lag-56.network.virginmedia.net -    0 |   19 |   19 |   11 |   11 |   14 |   13 |
|    drkn-bh1-ia1.network.virginmedia.net -    0 |   19 |   19 |   11 |   12 |   14 |   12 |
|                     unreal.miasma.rocks -    0 |   19 |   19 |   12 |   12 |   15 |   13 |
|________________________________________________|______|______|______|______|______|______|


not relevant to game server but this was messed up too (was about 100 down when it wasn't happy)
Title: Re: Routing issues
Post by: Piglet on September 26, 2022, 12:44
Woah! That's a nice ping.

They've been running cables round here but aren't ready to connect up yet.
Title: Re: Routing issues
Post by: hagis on September 26, 2022, 17:53
Quote from: Piglet on September 26, 2022, 12:44
Woah! That's a nice ping.

They've been running cables round here but aren't ready to connect up yet.

ya looks like they came up with a better route between vodafone and virgin :)

hopefully they are putting the fibre in the pavement round your way, on mine they took it to the telephone pole and the fibre goes across 2 other gardens in the air - not ideal as there are trees and I can bet at some point it will snap(!)
Title: Re: Routing issues
Post by: hagis on September 26, 2022, 18:42
fs... well vodafone... I give them 2/10 for customer service. every 2 calls in 10 you might get someone who can help,. the other times they make things worse,. I called them about the packet loss - ICMP is fine but still see a little (not as bad as it was) on the server itself..

anyway - instead of doing anything useful they just went and reset my router - I asked them not to and they did it anyway,.. so all my config (like my private address space is not default etc) is wiped... oh well.. just don't expect someone to help
Title: Re: Routing issues
Post by: KoTELLO on December 03, 2022, 16:48
In the last two weeks it has become unplayable for me. Packet loss and fluctuating ping appeared. Periodically, weapons, bullets, players and vehicles disappear.

mtr:
https://disk.yandex.ru/i/ESjpNm8BIjkxEw

Title: Re: Routing issues
Post by: Nardaq_NL on December 03, 2022, 18:19
Seems there is a dodgy route from/to DE. nothing much we can do about it. You can contact your IPS about this issue.
Title: Re: Routing issues
Post by: Gil-galad on May 21, 2023, 23:18
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 (https://ibb.co/BZKKg70))

So I know it's my ISP's fault, and i'll perhaps go to another one soon, but anyway, why the discrepancy?
Title: Re: Routing issues
Post by: Nardaq_NL on May 22, 2023, 10:54
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.

(https://media.discordapp.net/attachments/1034153295704510584/1110141017975431178/image.png)


and this is how it not suppose to look like. (virginmedia issue 1,5 month ago)
(https://cdn.discordapp.com/attachments/1034153295704510584/1110142196834906163/image.png)
Title: Re: Routing issues
Post by: Gil-galad on May 24, 2023, 16:22
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.
Title: Re: Routing issues
Post by: Resike on May 24, 2023, 22:53
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.
Title: Re: Routing issues
Post by: holyspam on June 26, 2023, 20:14
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.

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.
Title: Re: Routing issues
Post by: Stealer on June 27, 2023, 21:43
Quote from: Resike on May 24, 2023, 22:53
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.

Very good points that is in effect a DDOS and increasing the interval will help to prevent the server from assuming you are DDOS'ing, also depends which ports you use for the pings, given the amount of data and packets sent during gameplay on the servers.  8)