Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 High Latency - US server

views
     
cowithgun
post Sep 26 2014, 12:18 PM

A cow that can play notebook & phone
*******
Senior Member
2,248 posts

Joined: Sep 2010
About the AU server, I ran tcpdump (actually wireshark) a couple days ago and discovered that no matter if you set "OnlineService.Matchmaking.ServerPool=AU1" or not, it will still go to US server.

Today I ran it again, seem like it's back to normal. During gameplay, it will constantly connect to (for me) 12.130.244.193 and the actual game server depending on server you chose:

US Server: 12.130.245.39
AU Server: 103.4.114.11

Did a traceroute to these IP, I discovered something else. Unifi line actually hop less and faster to US server (today!). Yes 4G still using reroute in Japan and HongKong.

Just for info, you also can use http://us-looking-glass.battle.net/ to see how the packet travel from Blizzard to you. biggrin.gif It changes daily! LOL! Yesterday, both Unifi and 4G uses hop in Japan and HongKong. Today, Unifi uses hop in Singapore. 4G Yes still using Japan (which sloooowwww...)


cowithgun
post Sep 26 2014, 04:47 PM

A cow that can play notebook & phone
*******
Senior Member
2,248 posts

Joined: Sep 2010
QUOTE(I<3LYN @ Sep 26 2014, 02:06 PM)
you missed something.

there are 2 separated 'connections'

battle.net authentication/communication uses tcp
game uses udp packets

the client will first authenticate with the actual battle.net server and its authentication service
then the client/battle.net will decide which game server to connect.
running tcpdump (or wireshark with the wrong parameters) will not get you anything.

regardless of which game server you choose, the client will always authenticated at the us/eu/asia server first.
*
i have the same understanding, that is why i said, those are capture during gameplay.

US Server: 12.130.245.39
AU Server: 103.4.114.11

if you trace those IP, you will see that they are hosting in the respective country, which indicates that this is the game server and not the authentication server. and again, i was checking the network packet during game play not the authentication process.

another thing, contrary to popular believe, D3 game play use TCP connection and not UDP. smile.gif

ps:

QUOTE
running tcpdump (or wireshark with the wrong parameters) will not get you anything.
are u indicating that i may not know how to use tcpdump/wireshark? i am just a little, slightly, offended with that comment... sad.gif

This post has been edited by cowithgun: Sep 26 2014, 05:36 PM

 

Change to:
| Lo-Fi Version
0.0156sec    0.40    6 queries    GZIP Disabled
Time is now: 27th November 2025 - 12:52 AM