Arthurdent [CDEV] Posted December 28, 2016 Report Share Posted December 28, 2016 Comparable east coast trace : C:\WINDOWS\system32>tracert sunrise.net-7.org Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 1 ms 2 ms 2 ms 192.168.1.1 2 13 ms 23 ms 21 ms .mc.videotron.ca [] 3 20 ms 15 ms 21 ms 10.170.182.81 4 16 ms 19 ms 18 ms ix-et-9-1-0-0.tcore1.MTT-Montreal.as6453.net [64.86.31.61] 5 26 ms 24 ms 24 ms if-ae-0-2.tcore2.MTT-Montreal.as6453.net [216.6.115.90] 6 24 ms 26 ms 23 ms if-ae-5-2.tcore2.N0V-New-York.as6453.net [64.86.226.58] 7 23 ms 27 ms 29 ms if-ae-2-2.tcore1.N0V-New-York.as6453.net [216.6.90.21] 8 31 ms 25 ms 29 ms if-ae-7-2.tcore1.NTO-New-York.as6453.net [63.243.128.25] 9 26 ms 23 ms 27 ms if-ae-9-2.tcore1.N75-New-York.as6453.net [63.243.128.122] 10 25 ms 32 ms 26 ms ae9.edge1.NewYork.Level3.net [4.68.62.185] 11 * * * Request timed out. 12 76 ms 98 ms 79 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 71 ms 74 ms 79 ms sunrise.net-7.org [38.130.197.232] 16 75 ms 70 ms 72 ms sunrise.net-7.org [38.130.197.232] Trace complete. Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 28, 2016 Report Share Posted December 28, 2016 Just ran another one: C:\>tracert sunrise.net-7.org Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 6 ms 17 ms 18 ms 10.213.80.1 2 12 ms 13 ms 13 ms midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169] 3 * * * Request timed out. 4 * * * Request timed out. 5 58 ms 21 ms 21 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218] 6 29 ms 29 ms 29 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] 7 * * * Request timed out. 8 95 ms 103 ms 343 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] 9 100 ms 98 ms 97 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194] 10 173 ms 144 ms 103 ms lag-5.ear3.NewYork1.Level3.net [4.68.72.9] 11 * * * Request timed out. 12 151 ms 152 ms 161 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 2660 ms 170 ms 154 ms sunrise.net-7.org [38.130.197.232] 16 344 ms 145 ms 140 ms sunrise.net-7.org [38.130.197.232] Trace complete. Quote Link to comment Share on other sites More sharing options...
Kyp [LDEV] Posted December 28, 2016 Report Share Posted December 28, 2016 Ok, I had a theory and tried something (not going to explain to keep the control in a controlled experiment) but please monitor some more and let me know if the high ping to sunrise.net-7.org disappears. also, took a look on google for aorta.net, seems we aren't the only folks seeing issue through there for games:https://www.google.com/search?q=aorta.net+problems&rlz=1C1ASUM_enUS487US487&oq=aorta.net+problems&aqs=chrome..69i57.2498j0j7&sourceid=chrome&ie=UTF-8#q=aorta.net+high+ping Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 28, 2016 Report Share Posted December 28, 2016 (edited) Hi Kyp, Just saw your post and ran another TRaceRT for you at 18:38 GMT C:\>tracert sunrise.net-7.org Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 12 ms 20 ms 18 ms 10.213.80.1 2 20 ms 34 ms 19 ms midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169] 3 * * * Request timed out. 4 * * * Request timed out. 5 143 ms 22 ms 22 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218] 6 61 ms 42 ms 34 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] 7 * * * Request timed out. 8 232 ms 108 ms 109 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] 9 105 ms 104 ms 103 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194] 10 120 ms 109 ms 110 ms lag-5.ear3.NewYork1.Level3.net [4.68.72.9] 11 * * * Request timed out. 12 141 ms 152 ms 296 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 792 ms 149 ms 160 ms sunrise.net-7.org [38.130.197.232] 16 149 ms 139 ms 139 ms sunrise.net-7.org [38.130.197.232] Trace complete. Looks better than before and I have been logged in on 2 clients with no drops/CTD etc for almost 40 minutes. Reran the TraceRT again at 18:46 GMT: C:\>tracert sunrise.net-7.org Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 12 ms 288 ms 20 ms 10.213.80.1 2 17 ms 16 ms 17 ms midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169] 3 * * * Request timed out. 4 * * * Request timed out. 5 18 ms 22 ms 110 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218] 6 29 ms 92 ms 29 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] 7 * * * Request timed out. 8 99 ms 103 ms 121 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] 9 93 ms 94 ms 243 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194] 10 415 ms 221 ms 343 ms lag-5.ear3.NewYork1.Level3.net [4.68.72.9] 11 * * * Request timed out. 12 148 ms 145 ms 163 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 147 ms 156 ms 405 ms sunrise.net-7.org [38.130.197.232] 16 158 ms 140 ms 145 ms sunrise.net-7.org [38.130.197.232] Trace complete. Edited December 28, 2016 by YetiGBR1 Added extra info Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 28, 2016 Report Share Posted December 28, 2016 Update (after falling asleep at the kb) time: 20:43 GMT Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 12 ms 22 ms 21 ms 10.213.80.1 2 22 ms 23 ms 23 ms midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169] 3 * * * Request timed out. 4 * * * Request timed out. 5 26 ms 28 ms 57 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218] 6 34 ms 219 ms 125 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] 7 * * * Request timed out. 8 96 ms 104 ms 105 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] 9 358 ms 103 ms 104 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194] 10 104 ms 103 ms 102 ms lag-5.ear3.NewYork1.Level3.net [4.68.72.9] 11 * * * Request timed out. 12 147 ms 176 ms 190 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 268 ms 159 ms 178 ms sunrise.net-7.org [38.130.197.232] 16 150 ms 145 ms 138 ms sunrise.net-7.org [38.130.197.232] Trace complete. Gating and lost connection to server, error msg was "Server failed to respond to sector handover" Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 29, 2016 Report Share Posted December 29, 2016 Further update client is "awaiting Master HandOff" : 00:07 GMT 29th Dec 2016 C:\>tracert sunrise.net-7.org Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 22 ms 18 ms 61 ms 10.213.80.1 2 49 ms 22 ms 34 ms midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169] 3 * * * Request timed out. 4 * * * Request timed out. 5 28 ms 21 ms 21 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218] 6 30 ms 28 ms 31 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] 7 * * * Request timed out. 8 96 ms 712 ms 191 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] 9 133 ms 105 ms 100 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194] 10 100 ms 103 ms 97 ms lag-5.ear3.NewYork1.Level3.net [4.68.72.9] 11 * * * Request timed out. 12 180 ms 144 ms 418 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 13 * * * Request timed out. 14 * * * Request timed out. 15 149 ms 152 ms 149 ms sunrise.net-7.org [38.130.197.232] 16 516 ms 159 ms 148 ms sunrise.net-7.org [38.130.197.232] Trace complete. Quote Link to comment Share on other sites More sharing options...
Bluemeanie Posted December 29, 2016 Report Share Posted December 29, 2016 Tonight is horrible. Trying to play 4 toons, at least 1 locks up every 5-10 minutes. Gating looses one almost every time. Ran a ping to sunrise.net-7.org for 50 passes, all under 50ms. Tracing route to sunrise.net-7.org [38.130.197.232] over a maximum of 30 hops: 1 <1 ms 1 ms <1 ms 192.168.1.1 2 9 ms 19 ms 8 ms 10.52.112.1 3 8 ms 10 ms 11 ms tenngig1-8.orld53-var1.bhn.net [72.31.195.118] 4 10 ms 14 ms 11 ms ten0-15-0-11.orld71-car1.bhn.net [72.31.194.98] 5 12 ms 13 ms 19 ms 72-31-188-170.net.bhntampa.com [72.31.188.170] 6 14 ms 13 ms 16 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66 .109.6.98] 7 13 ms 10 ms 12 ms ae-1.bar2.Orlando1.Level3.net [4.68.111.17] 8 * * * Request timed out. 9 19 ms 18 ms 19 ms HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86] 10 * * * Request timed out. 11 * * * Request timed out. 12 21 ms 19 ms 21 ms sunrise.net-7.org [38.130.197.232] 13 20 ms 20 ms 20 ms sunrise.net-7.org [38.130.197.232] Trace complete. C:\Users\Bill> Quote Link to comment Share on other sites More sharing options...
Kyp [LDEV] Posted December 29, 2016 Report Share Posted December 29, 2016 all we can give you on that Bluemeanie, is that we'd need something like a packet capture to see if anything's being dropped. Looks like traffic is fine. The more clients you use, the more risk you run of packets being lost or misdirected, and with UDP that's a problem because packets are not retransmitted, that's specifically why we don't support it. Quote Link to comment Share on other sites More sharing options...
Bluemeanie Posted December 29, 2016 Report Share Posted December 29, 2016 (edited) What I don't understand is that until just over 2 weeks ago everything was fine. What changed? Oh, I have had this problem with just one toon online as well. Also last night I saw where people were dc'ing locking up etc. Ran a ping and it was horrible, and a tracert was just as bad however I never did dc or lockup. Edited December 29, 2016 by Bluemeanie interrupted by dogs wanting out Quote Link to comment Share on other sites More sharing options...
Kyp [LDEV] Posted December 29, 2016 Report Share Posted December 29, 2016 That's just the thing, nothing really has changed since we moved over to the new server. Quote Link to comment Share on other sites More sharing options...
Zackman [LDEV] Posted December 29, 2016 Report Share Posted December 29, 2016 What i can see is a very "jumpy" communication beginning in this "aorta" net. The spikes in responses look very typical for an overloaded network. Explanation: Whenever more traffic is occuring, the first things delayed are UDP packets. Why? These are the regulary used network protocol for attacks like DDos etc. If traffic is overloading the ISP switches, UDP is even dropped. This is when we say "packet drops / packet loss". There was no crap like DDos when this game was created, but it's a common problem today. US-eLections, Trump, China, Russia<->Obama - this all will cause many bad guys in the world starting cyberwar, attacking the US-infrastructure. See the "Norse" Monitor: http://map.norsecorp.com/#/ This one is showing network attacks worldwirde in real time. We had this problems before - they are not new, but they are now more. I think it's based on the routing to the new servers. The solution is not moving servers around till we find a "good location", because a "good location" today could be a bad one tomorrow. 1 Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 29, 2016 Report Share Posted December 29, 2016 (edited) Has the DNS entry canged for sunrise.net-7.org? from sunrise.net-7.org [38.130.197.232] to 141.8.225.226 reason I ask just crashed and did a tracert again and this came back: Date/Time 29th Dec 2016 @ 11:05am GMT (approx -+ or - 2-3 mins) C:\>tracert sunrise.net7.org Tracing route to sunrise.net7.org [141.8.225.226] over a maximum of 30 hops: 1 17 ms 21 ms 21 ms 10.213.80.1 2 186 ms 23 ms 23 ms midd-core-2b-xe-203-0.network.virginmedia.net [62.252.68.185] 3 * * * Request timed out. 4 * * * Request timed out. 5 135 ms 57 ms 51 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158] 6 48 ms 50 ms 60 ms TenGE13-2.br02.ams01.pccwbtn.net [80.249.209.37] 7 174 ms 211 ms 175 ms HundredGE0-3-0-0.br04.dal01.pccwbtn.net [63.223.32.66] 8 336 ms 224 ms 181 ms datafoundry.te0-1-0-8.br04.dal01.pccwbtn.net [63.218.23.119] 9 184 ms 655 ms 361 ms 209-99-48-54.fwd.datafoundry.com [209.99.48.54] 10 177 ms 168 ms 168 ms 141.8.225.226 Trace complete. Edited December 29, 2016 by YetiGBR1 Quote Link to comment Share on other sites More sharing options...
Zackman [LDEV] Posted December 29, 2016 Report Share Posted December 29, 2016 sunrise.net-7.org (sunrise.net-7.org) instead of sunrise.net7.org 1 Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 29, 2016 Report Share Posted December 29, 2016 Well spotted Zackman I think I need more coffee : Quote Link to comment Share on other sites More sharing options...
YetiGBR1 Posted December 29, 2016 Report Share Posted December 29, 2016 (edited) Having established it is not client/server related and is infact an "internet infrastructure Issue" I have resorted to running a single client and dealing with the inconvinience until it apperars to become more stable. I would like to give a Massive Thankyou to all that have looked into the issues on my/our behalf. All the best, YetiGBR the insane. Edited December 29, 2016 by YetiGBR1 Quote Link to comment Share on other sites More sharing options...
Bluemeanie Posted January 5, 2017 Report Share Posted January 5, 2017 Not sure if it's related, but I noticed that when the hang occurs when gating that there's a message behind the game. It goes away when killing the game with task manager, so I never saw what it said. Well this morning on a hang while gating, I remembered to look at the message, it says "Server Failed to respond to sector login". Quote Link to comment Share on other sites More sharing options...
Zackman [LDEV] Posted January 6, 2017 Report Share Posted January 6, 2017 That is VERY related. It means, that your local client is sending packets to the server on a specific port, while the server is sending packets back on a diff. port. What happens when gating: Each sector has its own UDP port. When you gate (or dock), the server will send a packet basically saying "Hey client, switch over from channel (port) 5 to channel 10, we will communicate on channel 10 in the new sector". Whenever that packet isn't arriving at your computer (many reason possible here), your client continues communicating on that old port/channel, while the server is awaiting your comunication on that new port - and there is no communication from you, so the comm. is lost/broken. So at one point your client will say "Server failed to respond to sector login" - while the truth is "Client failed to continue talking to server on the changed sector port". This all comes back to corrupted network communication. It could be a dropped packet, which happens OFTEN if there is load on the providers network, because UDP packets are the first being dropped. I know it sounds like a broken record ("lost packet") but unfortunatly this is exactly what happens. It could be also our server, dropping that packet for a reason. We DID have packet loss in the past, but it raised a lot after moving to the new server. Since there is virtualization in the chain, it becomes very hard to track - but we DO think it happens somewhere in the virtual switch. Anyway, this is outside of the server code, it's an issue with the server/network administration. 1 Quote Link to comment Share on other sites More sharing options...
Zarg Posted January 27, 2017 Author Report Share Posted January 27, 2017 Looks like the maintenance in January cleaned this right up. Thanks a bunch! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.