Jump to content
Eternal Lands Official Forums
Sign in to follow this  
saxum

Periods of disconnect since server moved to Canada

Recommended Posts

I have suffered like many players with the DDoS attacks on EL and commend the move of the servers to a provider who provides some level of DDoS protection but have seemed to encounter an unexpected side affect - instability at certain points in game where it appears I can receive data from EL (players and bots move) but can only sporadically react sometimes resulting in duplicate use of items and time outs. I had grue issues with old server but nothing like this.

 

I asked for help / reported issue as it states in channel 6 and the comments I got it was local because no one (debatable since others may not be as persistent as I) but as clearly showed by traceroute it is all in Canada. Oh and despite report of Wireless Broadband Router I am directly connected to router and not using WiFi; router has wireless capability with non-trivial, non-default password installed. I had no issue during this period connecting to other servers including downloading large files and yes I tried stopping all downloads to see if that helped.

 

The problem is in Canada where the new servers are located.

I have included several trace routes below.

Note: #11 is always Request timed out - trace not allowed.

 

 

Ping goes from normal 20-60 ms to 5 digit ms and have had periods where I can log in and not do anything. As I said above I am receiving data for I had food level go from 100 to 40 (20 minutes) before I could do as little as put on power saving cloak. It happens at different times of day including busy time and at middle of night where there are 100 users logged in, most of them AFK. One occurred in middle of invance and three times I froze; not something that which encourages players to risk expensive gear and rostos so I am playing a lot more careful now.

 

I am no expert despite Network Engineer being in my title but this appears to be a server which is having trouble with one or more channels, with those channels server a portion of its connections probably by area. Maybe a card is having issue receiving until computer realizes it and resets it.

 

Suggestions on how to solve issue or gather more data to diagnose issue?

 

 

 

Sample trace routes below:

 

 

Tracing route to game.eternal-lands.com [192.99.21.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 8 ms 8 ms L100.WASHDC-VFTTP-122.verizon-gni.net [70.110.27.1]
3 10 ms 13 ms 10 ms G0-6-2-4.WASHDC-LCR-21.verizon-gni.net [100.41.197.196]
4 9 ms 11 ms 11 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 12 ms 10 ms 11 ms 0.xe-5-1-3.XL3.IAD8.ALTER.NET [152.63.7.245]
6 12 ms 10 ms 12 ms TenGigE0-6-4-0.GW1.IAD8.ALTER.NET [152.63.35.145]
7 105 ms * 12 ms teliasonera-gw.customer.alter.net [152.179.50.234]
8 12 ms 11 ms 11 ms ash-bb3-link.telia.net [80.91.252.88]
9 70 ms 16 ms 18 ms nyk-bb1-link.telia.net [62.115.138.22]
10 28 ms 17 ms 19 ms nyk-b2-link.telia.net [213.155.130.28]
11 * * * Request timed out.
12 314 ms * * bhs-g1-6k.qc.ca [198.27.73.205]
13 * 71 ms * vac3-0-a9.qc.ca.vaccum [198.27.73.245]
14 137 ms * 137 ms vac3-1-n7.qc.ca.firewall [198.27.73.242]
15 * 136 ms * vac3-2-n7.qc.ca.tilera [198.27.73.247]
16 * 136 ms 136 ms vac3-3-n7.qc.ca [198.27.73.237]
17 * * * Request timed out.
18 324 ms 317 ms 317 ms game.eternal-lands.com [192.99.21.222]
Trace complete.

 

 

 

Tracing route to game.eternal-lands.com [192.99.21.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 8 ms L100.WASHDC-VFTTP-122.verizon-gni.net [70.110.27.1]
3 10 ms 18 ms 10 ms G0-6-2-4.WASHDC-LCR-21.verizon-gni.net [100.41.197.196]
4 13 ms 10 ms 11 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 67 ms 43 ms 8 ms 0.xe-7-0-0.XL3.IAD8.ALTER.NET [152.63.34.201]
6 15 ms 14 ms 11 ms TenGigE0-4-2-0.GW1.IAD8.ALTER.NET [152.63.38.254]
7 22 ms 23 ms 22 ms teliasonera-gw.customer.alter.net [152.179.50.234]
8 27 ms 27 ms 25 ms ash-bb3-link.telia.net [80.91.252.88]
9 36 ms 40 ms 85 ms nyk-bb1-link.telia.net [62.115.138.22]
10 32 ms 31 ms 58 ms nyk-b2-link.telia.net [213.155.130.28]
11 * * * Request timed out.
12 * 451 ms * bhs-g1-6k.qc.ca [198.27.73.205]
13 * 68 ms * vac3-0-a9.qc.ca.vaccum [198.27.73.245]
14 151 ms 150 ms * vac3-1-n7.qc.ca.firewall [198.27.73.242]
15 * * * Request timed out.
16 * 148 ms * vac3-3-n7.qc.ca [198.27.73.237]
17 * * * Request timed out.
18 * 424 ms 428 ms game.eternal-lands.com [192.99.21.222]
Trace complete.
Tracing route to game.eternal-lands.com [192.99.21.222]
over a maximum of 30 hops:
1 <1 ms 8 ms 4 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 8 ms L100.WASHDC-VFTTP-122.verizon-gni.net [70.110.27.1]
3 9 ms 10 ms 12 ms G0-6-2-4.WASHDC-LCR-21.verizon-gni.net [100.41.197.196]
4 16 ms 12 ms 13 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 12 ms 11 ms 11 ms 0.xe-5-1-3.XL3.IAD8.ALTER.NET [152.63.7.245]
6 29 ms 13 ms 16 ms TenGigE0-6-2-0.GW1.IAD8.ALTER.NET [152.63.35.141]
7 12 ms 13 ms 10 ms teliasonera-gw.customer.alter.net [152.179.50.234]
8 17 ms 16 ms 12 ms ash-bb3-link.telia.net [80.91.252.88]
9 18 ms 16 ms 17 ms nyk-bb1-link.telia.net [62.115.138.22]
10 31 ms 17 ms 15 ms nyk-b2-link.telia.net [213.155.130.28]
11 * 51 ms * nwk-1-6k.nj.us [178.32.135.212]
12 * 311 ms * bhs-g1-6k.qc.ca [198.27.73.205]
13 * 64 ms 61 ms vac3-0-a9.qc.ca.vaccum [198.27.73.245]
14 * 140 ms 139 ms vac3-1-n7.qc.ca.firewall [198.27.73.242]
15 135 ms * 136 ms vac3-2-n7.qc.ca.tilera [198.27.73.247]
16 * * 139 ms vac3-3-n7.qc.ca [198.27.73.237]
17 * * * Request timed out.
18 204 ms 200 ms * game.eternal-lands.com [192.99.21.222]
19 232 ms * 213 ms game.eternal-lands.com [192.99.21.222]
Trace complete.

 

Share this post


Link to post
Share on other sites

My problem occurred on March 28 and March 29 but will see if improvement seen after repairs.

Share this post


Link to post
Share on other sites

Still occurs fine for a while and then same symptoms

Server latency: 18519 ms
Server latency: 38497 ms

 

5:03>: Disconnected from server!
5:07>: Disconnected from server!
5:12>: Disconnected from server!
5:18>: Disconnected from server!
5:27>: Disconnected from server!
etc. Same pattern with tracert in Canada
Edited by saxum

Share this post


Link to post
Share on other sites

No I did not for as the trace route states it clearly is occurring in Canada and my ISP is not in Canada.

Share this post


Link to post
Share on other sites

The place to start is with your ISP, so they can check to see where they are sending the data as well as contacting other ISP's. Obviously there is something close to you that is routing the packets poorly instead of getting them on to OVH's network quickly like most of the other people have.

 

Yes, the link upgrades Entropy mentions may help, but those links only have problems with OVH is under a heavy DDoS (heavier then has been leveled against EL).

Share this post


Link to post
Share on other sites

A weak argument, as I don't rely that much on low latency, but still: I've been hosting the OpenTTD services (including the master game server to connect players to servers as well as the ingame online content which distributs content required to join many servers - both services where players easily complain about latency. But the machine also serves wiki, repositories and website). It's based in the French data centre of OVH for a few years now. Even in times of DDOS on other websites, this did not seem to have detrimental effect on the availability of our services. Aas far as I recall, in like 4 years we experienced no single time where servers were not available due to network issues - and our userbase likely is equivalent or even larger than EL's - so the statistics are quite decent. OVH seem to be pretty good at diffusing the impact of network incidents.

Edited by Elke

Share this post


Link to post
Share on other sites

OVH has specifically stated that several links into thri network are being upgraded specifically to avoid problems during DDoS. While that may not help hid problem, there is a case it might. I actually suspect some routing table someplace are faulting causing bottlenecks.

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoticons maximum are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×