Ping problem

Post Reply
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Ping problem

Post by =IAM= Allen »

Ever since the new master server fix has gone live I've had problems with my ping. It starts at my norm 78 to 83 but soon climbs to 180 an will hold there for 15 to 30 min. This high ping makes any infantry map unplayable. I have tired router/modem/computer restarts. They have no efffect.

EA117 is the only sever I have seen this problems. Moongamers and =SoC= Chaos Phillies are quite fine when I play on them. Will try to play on EA117 after all of the players are gone and see if it is a player causing the ping to jump (Seen this before) or if the problem persists when I'm by my self.
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

I would have to initially assume that the updated BF1942.EXE isn't related to the cause, especially when EA117 is the only server you're seeing the issue with. But we're not at the shutdown yet, so you can definitely put back the original BF1952.EXE to test/verify that the issue continues regardless of which .EXE you're using.

(You'll be able to test things like that even after the shutdown too; you just have to use one of the other workarounds to avoid the hang issue, in addition to testing the original/non-fixed .EXE. For now you don't have to worry about avoiding the hang issue, because it hasn't happened yet.)

The only thing even remotely close to that which comes to mind for me is the issues I see when trying to run Windows 8 or Windows 8.1. On the exact same machine where I can play under Windows 7 SP1 without issue, rebuilding to use Windows 8 or Windows 8.1 instead will "initially play fine", but as soon as I'm "in a crowd" with multiple people or vehicles in close vicinity, it lags so very bad. (Though I've never watched closely enough to say my ping is affected.) Reverting back to Windows 7 SP1 and that symptom never occurs.

But yours sounds more like a straight-forward "the route between me and EA117 is slower / higher-latency than it normally is", if playing other servers isn't showing the same thing.

-Trench
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

PC is Win 7. High ping is happening with old EA and new patched .exe. I get the same 175 to 180 high ping from EA117 by Command Prompt using Ping 8.12.64.130. So I know the exe has nothing to do with it. I also get the same thing if I ping from another computer in the house via Command Prompt ping.

I just left Moongamers and it had about 56 players with no probs. I know Moongamers is now in TX. They move to TX from Chicago. My Moongamers ping is in the same range of 78 to 83 so I know Moon and EA117 are not too far apart.

I know when the new master thing was being changed to dynamic set up one of the admins (Don't know what one but it was by yellow text) came in and asked if pings were changed. Me and some others had pings that had jumped.
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

Interesting. Well hopefully whichever admin that was will pop in and shed some more light on that.

There isn't any change-over that has occurred on the EA117 server itself that I'm aware of, because nothing has been shut down yet. We want for the EA117 server to continue dynamically registering with master.gamespy.com for as long as that master will be available, which is sometime between May 31 and June 30.

No "change over of the EA117 server" was required to get the server visible on "master.bf1942.sk", because that alternate server just has a non-dynamic static list right now, which includes EA117. So using the alternate master lets you find EA117, but not because we're registering with it yet.

Not to mention that I would have a hard time suggesting why a change of the /etc/hosts would affect player ping latency.

-Trench
S.O.S
Retired Admin
Retired Admin
Posts: 494
Joined: May 22nd, 2009, 11:41 pm

Re: Ping problem

Post by S.O.S »

I had the same issue with Allen. My ping jumps from around 60 to 150. The game is not choppy but my shot-lead is definitely messed up. No change in my PC when this started to happen a few days ago. Haven't tried other servers yet. It will go back to normal by itself after a while. One or two other players reported the ping jump too but most seem to be fine. My impression is the affected guys are from the west coast, but I could be wrong.
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

I'm on the west coast. It did go back norm about 8:12PM west coast time. About 4 or 5 players other players had there pings drop as well. ))AhDaHua(( was one of the players effected. His ping dropped fron 150-153 down to 50-53. Also of note. The drop of ping is not instantly. It takes about 1 or 2 mins for the ping to drop (or rise).

It seem that any player effect by this has a 100+ added to there norm ping. As S.O.S pointed out game is not choppy but shot-lead is messed up and well being shot at is worse. Trying to take any cover is useless. I run into an open door and I get killed while being 2 feet inside the building.
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

For an issue like that, one way to confirm it's "somewhere in the middle" of the route and not at your end or EA117 / the game server host's end is to take a traceroute. Take a baseline now when the issue isn't happening and your ping is normal, and then take a traceroute again if and when the issue re-surfaces. So that you can see at which point in the route the additional latency appears to be introduced.

For example, here are the eight hops between me and the game server host network:
C:\>tracert 8.12.64.130

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms [NSA REDACTED]
3 8 ms 6 ms 7 ms G0-14-2-1.DLLSTX-LCR-22.verizon-gni.net [130.81.221.239]
4 8 ms 4 ms 5 ms ae8-0.DFW9-BB-RTR2.verizon-gni.net [130.81.162.160]
5 8 ms 6 ms 7 ms 0.xe-3-2-1.BR2.DFW13.ALTER.NET [152.63.100.109]
6 8 ms 6 ms 7 ms 204.255.168.158
7 7 ms 6 ms 7 ms ae9.cr1.dfw1.us.nlayer.net [69.31.63.168]
8 7 ms 6 ms 7 ms as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net [69.31.63.238]
9 7 ms 6 ms 7 ms 8.12.64.130

Trace complete.
When the issue is occurring, if all hops except the first one are drastically higher latency, you would suspect something at your end / the cable modem's end / your ISP's end. If all hops were still the same and only the last one was slower, you would suspect something that the game server's end / the game server host ISP's end.

If the higher-latency hop is somewhere in the middle you're kinda SOL, and just have to hope the routing protocol notices and distributes the overloaded router or similar. (Though I have on occasion made calls to Comcast back when I was in Utah, when the traceroute showed that during problem periods the traffic between me and a game server on the West Coast was being shipped to Virginia and back first.)

-Trench
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

Roger. Took the ping now. Looks in the norm range and also took a tracert. Will report back if ping jumps back up.

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 7 ms 3 ms 1 ms 192.168.1.1
2 18 ms 5 ms 1 ms 192.168.0.1
3 75 ms 10 ms 10 ms adsl-76-193-79-254.dsl.chi2ca.sbcglobal.net [76.
193.79.254]
4 12 ms 12 ms 11 ms 63.200.183.194
5 12 ms 11 ms 10 ms 12.83.54.52
6 46 ms 49 ms 104 ms ggr4.sffca.ip.att.net [12.122.86.197]
7 36 ms 35 ms 36 ms ae0.sjc12.ip4.tinet.net [77.67.78.93]
8 79 ms 79 ms 78 ms xe-10-3-0.dal33.ip4.tinet.net [89.149.182.165]
9 82 ms 80 ms 78 ms gtt-gw.ip4.tinet.net [173.241.130.138]
10 82 ms 77 ms 77 ms as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net [69.31.6
3.238]
11 80 ms 78 ms 79 ms 8.12.64.130

Trace complete.
User avatar
i_am_not_your_father
Retired Admin
Retired Admin
Posts: 380
Joined: March 31st, 2009, 10:55 am

Re: Ping problem

Post by i_am_not_your_father »

I also noticed this same behavior and I am in the east coast. My ping jumped from 50 or so to 160.

IANYF
S.O.S
Retired Admin
Retired Admin
Posts: 494
Joined: May 22nd, 2009, 11:41 pm

Re: Ping problem

Post by S.O.S »

Maybe it's ISP related? I have AT&T Uverse, Allen seems to use AT&T DSL.
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

Okay new tracert.

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 14 ms 9 ms 3 ms 192.168.1.1
2 1 ms 5 ms 5 ms 192.168.0.1
3 11 ms 15 ms 11 ms adsl-76-193-79-254.dsl.chi2ca.sbcglobal.net [76.
193.79.254]
4 11 ms 17 ms 11 ms 63.200.183.194
5 14 ms 11 ms 13 ms 12.83.54.52
6 35 ms 34 ms 34 ms ggr4.sffca.ip.att.net [12.122.86.197]
7 36 ms 35 ms 38 ms ae0.sjc12.ip4.tinet.net [77.67.78.93]
8 * 80 ms 81 ms xe-8-3-2.dal33.ip4.tinet.net [141.136.111.98]
9 138 ms 136 ms 137 ms gtt-gw.ip4.tinet.net [173.241.130.138]
10 146 ms 141 ms 141 ms as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net [69.31.6
3.238]
11 143 ms 144 ms 143 ms 8.12.64.130

Trace complete.
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

=IAM= Allen wrote: 9 138 ms 136 ms 137 ms gtt-gw.ip4.tinet.net [173.241.130.138]
So pretty much all the difference in this gtt-gw.ip4.tinet.net hop. Which is still the same router you were passing through before, just now slower. Will be interesting to see if others with the ping issue happen to be passing through the same router, but not a lot to be done about it.

-Trench
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

Makes no since. When I first joined I was fine.

Also from what I can find is that the router causing the high ping is in Chicago, Illinois. This seem quite far to go since EA117 is in Kansas from what I can find. Hopefully other will do a tracert.
User avatar
i_am_not_your_father
Retired Admin
Retired Admin
Posts: 380
Joined: March 31st, 2009, 10:55 am

Re: Ping problem

Post by i_am_not_your_father »

I also have att uverse. tracert to 8.12.64.130 times out at hops 2,3,4, and 5; then it levels out until hop 12:
12 156 ms 162 ms 161 ms gtt-gw.ip4.tinet.net [173.241.130.138]

att support's mentality is that as long as you can surf the web and your download/upload speeds are close enough to what is expected then there is nothing wrong with their service.
User avatar
i_am_not_your_father
Retired Admin
Retired Admin
Posts: 380
Joined: March 31st, 2009, 10:55 am

Re: Ping problem

Post by i_am_not_your_father »

Note that it is possible that routers on the U-verse Network can be configured not to reply to ICMP requests thus the time outs. That would leave gtt-gw.ip4.tinet.net as the bottleneck.
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

Fark!

The 2 IPs above gtt-gw.ip4.tinet.net [173.241.130.138] according to ip-adress.com are in France! WTF....
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

=IAM= Allen wrote:The 2 IPs above gtt-gw.ip4.tinet.net [173.241.130.138] according to ip-adress.com are in France! WTF....
Yeah, I don't think that's actually true. tinet.net is registered by an Italian company, but these addresses could be physically anywhere despite that fact. The public registration info of networks and DNS names doesn't provide accurate physical location info, but everyone draws maps / states locations based on "whatever info is available."

-Trench
User avatar
i_am_not_your_father
Retired Admin
Retired Admin
Posts: 380
Joined: March 31st, 2009, 10:55 am

Re: Ping problem

Post by i_am_not_your_father »

I think it is something specific to 8.12.64.130. My ping never used to be this bad until a few days ago. ping is ok on another server I frequent.
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

8.12.64.130 is EA117....

Like I said Moongamers and =SoC= Chaos Phillies are quite fine. HKHP El Alamein (CD/ORIGIN) and Kaskingo - El Al - DC (Stats) *AKA DC bot server* are fine as well. It is something specific that happens to EA117. I don't know if it is an Admin logging in by remote? After all of the admins left last night ping went back to norm for CTF docks and weapons bunkers.
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

i_am_not_your_father wrote:I think it is something specific to 8.12.64.130. My ping never used to be this bad until a few days ago. ping is ok on another server I frequent.
Possibly, since we can't rule anything out without knowing the true root cause. But note that the data we're seeing from the traceroutes (albeit from only two examples thus far) can explain why it appears like "it's only EA117", too.

If the router at gtt-gw.ip4.tinet.net [173.241.130.138] is the one getting overloaded, ONLY if the route from your ISP takes you through there, and ONLY if the game server you want to get to is on the other side of that router, would you see the issue.

If you hit ANY other server that doesn't need to take you through that router, everything would be fine. (Or at least, you wouldn't have THAT particular problem.)

For example, my ISP would never take me through that route, and my ping isn't going up when your ping goes up. So I tend to believe that it's not EA117's server, but is a router close enough to the network EA117's game server host is connected to that MANY routes from several regions end up wanting to pass through that affected router.

-Trench
User avatar
=IAM= Allen
Member
Posts: 21
Joined: May 14th, 2014, 4:41 pm

Re: Ping problem

Post by =IAM= Allen »

I did a traceroute of Moongamers. My ping there is the same (+/- 2 or 3). It did not show me going through gtt-gw.ip4.tinet.net [173.241.130.138].
User avatar
Trench
Admin
Admin
Posts: 2908
Joined: May 22nd, 2012, 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: Ping problem

Post by Trench »

Yeah, if the traceroute that both =IAM= Allen and by i_am_not_your_father did was already showing +150ms at the gtt-gw.ip4.tinet.net [173.241.130.138] hop, you haven't even reached the EA117 game server yet at that point, so it actually is rather definitive that a change at the EA117 server isn't what's making the route suddenly slower at times.

We certainly can't know the true cause -- is this router suddenly overloaded with traffic which wasn't there before, is the router actually having a technical problem, is some other router shut down or temporarily taken out of service and now this router is trying to handle the additional load the other router used to handle, etc.

Definitely keep looking, and see if there are any other problem routes besides just this one coming through the gtt-gw.ip4.tinet.net [173.241.130.138] hop. But so far, it seems like this particular router is the "sudden change" which has made a bunch of player's pings wonky.

(Maybe Electronic Arts did not pay TinEt.net a fee to be put into the anti-net-neutrality "fast lane", so now EA game traffic is being assigned a lower quality of service. Ha ha, kidding... I hope.)

-Trench
User avatar
Payne N. Daiz
Member
Posts: 184
Joined: January 26th, 2009, 10:05 pm

Re: Ping problem

Post by Payne N. Daiz »

I don't have an answer these specific ping problems but I would recommend using these guys regardless. Might help with your ping too...

http://www.opendns.com/
Image
User avatar
SuperTesla
Member
Posts: 81
Joined: December 15th, 2013, 5:40 pm
Location: Pensacola, FL, USA
Contact:
United States of America

Re: Ping problem

Post by SuperTesla »

Trench wrote:F

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms [NSA REDACTED]
3 8 ms 6 ms 7 ms G0-14-2-1.DLLSTX-LCR-22.verizon-gni.net [130.81.221.239]
4 8 ms 4 ms 5 ms ae8-0.DFW9-BB-RTR2.verizon-gni.net [130.81.162.160]
5 8 ms 6 ms 7 ms 0.xe-3-2-1.BR2.DFW13.ALTER.NET [152.63.100.109]
6 8 ms 6 ms 7 ms 204.255.168.158
7 7 ms 6 ms 7 ms ae9.cr1.dfw1.us.nlayer.net [69.31.63.168]
8 7 ms 6 ms 7 ms as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net [69.31.63.238]
9 7 ms 6 ms 7 ms 8.12.64.130
?!!?!!??!!? TRENCH YOU'RE BEING SPIED ON BY THE NSA! GET OUTTA THERE!!!


:33:
Long live Catpantsia!

BF player since 2003
User avatar
i_am_not_your_father
Retired Admin
Retired Admin
Posts: 380
Joined: March 31st, 2009, 10:55 am

Re: Ping problem

Post by i_am_not_your_father »

i_am_not_your_father wrote:I think it is something specific to 8.12.64.130. My ping never used to be this bad until a few days ago. ping is ok on another server I frequent.
Correction - I meant gtt-gw.ip4.tinet.net [173.241.130.138] not 8.12.64.130.
Post Reply