New german server

[Apache]

Hey its impossible to play for me and few others(like higina). the Ping is over 500 and we dont know why. On the old community server it was perfect. What can we do?
Greez Jokey

[Necrophiliac]

Yea, saurus had the same problem for a short period of time. He was also had 450-500 ping but should be getting 25. Best to tell drk if he doesn't already know.

[drk]

I know. I don't know why. I mean it seems the problem is somewhere in your route to this server. If many of you have this issue we'll have to move a server again. Somewhere.  

[Apache]

OK I try again...Now 15PM and it works with 30 Ping

[Apache]

OK and on the evening agein over 400 

[Apache]

Hey I had a phone call from Unitymedia(our provider) and they told me that the problem isnt on their side. The only solution is to contact the developer of the game...

[Daemon]

Good luck with that.

[drk]

Found out "why" some of the people have 300-500 ping sometimes on the new server. Got lucky to ping from the server Jokey when he had this ping.

user@server:~$ traceroute 149.172.173.71
traceroute to 149.172.173.71 (149.172.173.71), 30 hops max, 60 byte packets
 1  172.31.1.1 (172.31.1.1)  0.210 ms  0.185 ms  0.171 ms
 2  10220.your-cloud.host (88.99.158.238)  0.158 ms  0.142 ms  0.127 ms
 3  static.193.158.99.88.clients.your-server.de (88.99.158.193)  32.943 ms  32.936 ms  32.923 ms
 4  85-10-219-65.clients.your-server.de (85.10.219.65)  0.658 ms 85-10-219-69.clients.your-server.de (85.10.219.69)  0.794 ms 85-10-219-65.clients.your-server.de (85.10.219.65)  1.027 ms
 5  85-10-250-213.clients.your-server.de (85.10.250.213)  0.351 ms  0.360 ms  0.343 ms
 6  core11.nbg1.hetzner.com (213.239.229.153)  0.313 ms core12.nbg1.hetzner.com (213.239.229.157)  0.362 ms  0.342 ms
 7  juniper5.dc2.nbg1.hetzner.com (213.239.229.166)  2.078 ms  2.071 ms  2.064 ms
 8  ae5-710.nbg40.core-backbone.com (81.95.15.5)  0.744 ms  0.692 ms  0.444 ms
 9  ae1-2001.fra10.core-backbone.com (81.95.15.162)  3.573 ms  3.579 ms  3.572 ms
10  ffm-b4-link.telia.net (62.115.9.225)  168.183 ms  168.151 ms  168.109 ms
11  213.46.177.9 (213.46.177.9)  168.112 ms  168.263 ms  168.377 ms
12  de-fra01b-rc1-ae30-0.aorta.net (84.116.134.165)  174.079 ms  173.930 ms de-fra01b-rc1-ae29-0.aorta.net (84.116.134.161)  174.029 ms
13  84.116.190.106 (84.116.190.106)  173.982 ms  173.808 ms  173.840 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
user@server:~$

As you can see there is "ffm-b4-link.telia.net" that makes huge jump. I don't know how many of you are going through this route and there is no guarantee that you escape it if we get new server location. I can't predict it.

When it's fine he has:

 1  172.31.1.1 (172.31.1.1)  0.085 ms  0.057 ms  0.039 ms
 2  10220.your-cloud.host (88.99.158.238)  0.193 ms  0.173 ms  0.160 ms
 3  static.193.158.99.88.clients.your-server.de (88.99.158.193)  36.385 ms  36.383 ms  36.370 ms
 4  85-10-219-65.clients.your-server.de (85.10.219.65)  0.729 ms  1.119 ms  1.064 ms
 5  static.85-10-250-209.clients.your-server.de (85.10.250.209)  0.229 ms 85-10-250-213.clients.your-server.de (85.10.250.213)  0.259 ms  0.281 ms
 6  core11.nbg1.hetzner.com (213.239.229.153)  0.273 ms  0.244 ms core12.nbg1.hetzner.com (213.239.229.157)  0.320 ms
 7  juniper5.dc2.nbg1.hetzner.com (213.239.229.166)  0.392 ms  0.385 ms  0.377 ms
 8  ae5-710.nbg40.core-backbone.com (81.95.15.5)  0.521 ms  0.499 ms  0.522 ms
 9  ae1-2001.fra10.core-backbone.com (81.95.15.162)  3.644 ms  3.670 ms  3.798 ms
10  ffm-b4-link.telia.net (62.115.9.225)  4.613 ms  4.646 ms  4.579 ms
11  213.46.177.9 (213.46.177.9)  4.790 ms  4.745 ms  4.686 ms
12  de-fra01b-rc1-ae29-0.aorta.net (84.116.134.161)  44.102 ms de-fra01b-rc1-ae30-0.aorta.net (84.116.134.165)  44.007 ms de-fra01b-rc1-ae29-0.aorta.net (84.116.134.161)  43.998 ms
13  84.116.190.106 (84.116.190.106)  10.703 ms  10.905 ms  10.938 ms

[Hakugei]

The only solution is to contact the developer of the game...

Since they know this is not true, they're just trying to shift the blame.
We don't have control over your connection.

[Groentjuh]

Knowing the bottleneck within the route is very useful. But now how to get telia.net to fix it... As I pointed out before, Hetzner is nice, but latency suffers at peak-load of their network. This is a perfect example of just that! Groentjuh & Girls likely has the very same issue for Apache.

[Apache]

Yea Groen on G&G I had the same problems...

[drk]

Yea Groen on G&G I had the same problems...

Do you still have problems on this server?
Could you try to join and watch your ping on the new NLD server? It's here: 185.111.74.90:11235

[Apache]

Do you still have problems on this server?
Could you try to join and watch your ping on the new NLD server? It's here: 185.111.74.90:11235
[/quote]
During the day there are no problems. Its the best Ping I ever had~25
And I joined this Server:185.111.74.90:11235 with a Ping between 35 and 40
But lets see what will hapen in later hours...
Thx for your commitment

[drk]

NLD server started to lag like crazy. Delays for com, for spawning etc. Got unplayable. In the same time GER has the same bad thing with telia

traceroute to 134.3.119.182 (134.3.119.182), 30 hops max, 60 byte packets
 1  172.31.1.1 (172.31.1.1)  0.180 ms  0.161 ms  0.150 ms
 2  10220.your-cloud.host (88.99.158.238)  0.139 ms  0.128 ms  0.143 ms
 3  static.193.158.99.88.clients.your-server.de (88.99.158.193)  26.037 ms  26.056 ms  26.049 ms
 4  85-10-219-65.clients.your-server.de (85.10.219.65)  0.653 ms  0.649 ms 85-10-219-69.clients.your-server.de (85.10.219.69)  0.793 ms
 5  85-10-250-213.clients.your-server.de (85.10.250.213)  0.239 ms static.85-10-250-209.clients.your-server.de (85.10.250.209)  0.268 ms  0.260 ms
 6  core11.nbg1.hetzner.com (213.239.229.153)  0.251 ms core12.nbg1.hetzner.com (213.239.229.157)  0.331 ms core11.nbg1.hetzner.com (213.239.229.153)  0.318 ms
 7  juniper5.dc2.nbg1.hetzner.com (213.239.229.166)  0.310 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.162)  0.294 ms juniper5.dc2.nbg1.hetzner.com (213.239.229.166)  0.329 ms
 8  ae5-710.nbg40.core-backbone.com (81.95.15.5)  0.406 ms  0.399 ms  0.391 ms
 9  ae1-2001.fra10.core-backbone.com (81.95.15.162)  3.612 ms  3.609 ms  3.498 ms
10  ffm-b4-link.telia.net (62.115.9.225)  590.872 ms  590.879 ms  590.832 ms
11  213.46.177.9 (213.46.177.9)  595.315 ms  595.401 ms  595.386 ms
12  de-fra04a-rc1-ae31-0.aorta.net (84.116.134.189)  624.381 ms  624.219 ms  624.229 ms
13  84.116.190.42 (84.116.190.42)  599.519 ms  599.894 ms  599.638 ms
                                                                                                         

[ValrogM]

I'm not able to join now.

After I joined the server, it loaded the map again and I got a message in red saying "Valrog(2) shares an IP with Valrog".

Now when I try to join the server, it says:

"Invalid packet data received from server (cmd was 5)

Packet dumped to gamebadpacket.dat"