Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12

Thread: The 2 IP Conflict in SEA Server

  1. #1
    Basic Member
    Join Date
    Dec 2013
    Posts
    30

    The 2 IP Conflict in SEA Server

    Whenever i play a game in SEA Server , i have either of the 2 IPs and each gives me different ping
    103.28.xxx.xx = 100-150 Ping (which i normally get)
    103.10.xxx.xx = 300+ Ping (unplayable..)
    Even though theres a high chance that i get 103.28.xx.xx IP, I still don't know which IP i will get whenever i search a match. Please fix it somehow anyhow..

  2. #2
    Basic Member
    Join Date
    Dec 2013
    Posts
    120
    Maybe you are transferred in 103.10.xxx.xx because the other one has high traffic and that is normal. Nothing to fix there.

  3. #3
    Banned
    Join Date
    May 2012
    Posts
    276
    Hi Nyuu cat, I feel very bad for you guys in SEA. This problem has happened for years and has resulted in low skilled SEA players invading my AUS servers.

    All I can say is launch cmd.exe and tracert the server, post it to the SEA server sticky and hope a dev sees it. Looking by the amount of pages that thread has, I certainly hope valve is working on a solution.

    Good luck and please don't join my server.

  4. #4
    Valve Developer
    Join Date
    Nov 2011
    Posts
    523
    This shouldn't be happening. Can you run 'tracert sgp-1.valve.net' and 'tracert sgp-2.valve.net' and post it here? Your traffic seems to be going two different directions when they shouldn't. The return path looks good using the direct path via PTCL from Singapore.

    Quote Originally Posted by Nyuucat View Post
    Whenever i play a game in SEA Server , i have either of the 2 IPs and each gives me different ping
    103.28.xxx.xx = 100-150 Ping (which i normally get)
    103.10.xxx.xx = 300+ Ping (unplayable..)
    Even though theres a high chance that i get 103.28.xx.xx IP, I still don't know which IP i will get whenever i search a match. Please fix it somehow anyhow..

  5. #5
    Basic Member
    Join Date
    Dec 2013
    Posts
    30
    Quote Originally Posted by milton View Post
    This shouldn't be happening. Can you run 'tracert sgp-1.valve.net' and 'tracert sgp-2.valve.net' and post it here? Your traffic seems to be going two different directions when they shouldn't. The return path looks good using the direct path via PTCL from Singapore.
    Tracert 'sgp-1.valve.net' (103.28)


    1 2 ms 1 ms 1 ms DD-WRT [192.168.1.1]
    2 32 ms * 20 ms 10.171.136.1
    3 23 ms 26 ms 22 ms 192.168.91.2
    4 13 ms 11 ms 20 ms 58-27-174-194.wateen.net [58.27.174.194]
    5 44 ms 41 ms * 58-27-174-65.wateen.net [58.27.174.65]
    6 21 ms 27 ms * 58-27-180-190.wateen.net [58.27.180.190]
    7 12 ms 11 ms 9 ms 58-27-174-26.wateen.net [58.27.174.26]
    8 25 ms 44 ms 41 ms 58-27-181-234.wateen.net [58.27.181.234]
    9 25 ms 25 ms 20 ms 58-27-174-34.wateen.net [58.27.174.34]
    10 * 51 ms 55 ms tw130-static117.tw1.com [119.63.130.117]
    11 * * * Request timed out.
    12 341 ms 321 ms 314 ms 203.208.175.149
    13 317 ms 329 ms 325 ms 203.208.190.206
    14 114 ms 116 ms 126 ms unknown.hwng.net [173.245.210.222]
    15 113 ms 122 ms 130 ms 103-28-54-225.valve.net [103.28.55.225]
    16 129 ms 141 ms 121 ms sgp-1.valve.net [103.28.54.1]

    Tracert sgp-2.valve.net (103.10)


    1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
    2 26 ms 25 ms 12 ms 10.171.136.1
    3 13 ms 14 ms 26 ms 192.168.91.2
    4 11 ms 9 ms 16 ms 58-27-174-194.wateen.net [58.27.174.194]
    5 10 ms 13 ms 15 ms 58-27-174-65.wateen.net [58.27.174.65]
    6 12 ms 11 ms 13 ms 58-27-180-190.wateen.net [58.27.180.190]
    7 8 ms 7 ms 9 ms 58-27-174-26.wateen.net [58.27.174.26]
    8 15 ms 10 ms 11 ms 58-27-181-234.wateen.net [58.27.181.234]
    9 13 ms 13 ms 21 ms 58-27-174-34.wateen.net [58.27.174.34]
    10 36 ms 46 ms 34 ms tw130-static117.tw1.com [119.63.130.117]
    11 31 ms 28 ms 33 ms tw255-static101.tw1.com [110.93.255.101]
    12 * * * Request timed out.
    13 189 ms 185 ms 171 ms xe-8-1-3.edge4.Frankfurt1.Level3.net [212.162.25.89]
    14 347 ms 323 ms 329 ms vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]
    15 326 ms 316 ms 316 ms ae-92-92.ebr2.Frankfurt1.Level3.net [4.69.140.29]
    16 317 ms 316 ms 320 ms ae-24-24.ebr2.London1.Level3.net [4.69.148.197]
    17 315 ms 315 ms 322 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
    18 317 ms 324 ms 325 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
    19 318 ms 329 ms 318 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]
    20 316 ms 335 ms 316 ms 4.69.135.185
    21 329 ms 321 ms 324 ms ae-61-61.csw1.SanJose1.Level3.net [4.69.153.2]
    22 324 ms 324 ms 321 ms ae-1-60.edge3.SanJose1.Level3.net [4.69.152.18]
    23 516 ms 516 ms 505 ms 4.53.28.6
    24 404 ms 403 ms 406 ms vlan905-an-cat6k-tl1.starhub.net.sg [203.118.3.173]
    25 417 ms 414 ms 403 ms anatll10.starhub.net.sg [203.118.7.17]
    26 328 ms 350 ms 331 ms 203.116.7.62
    27 308 ms 327 ms 314 ms 103-10-124-228.valve.net [103.10.124.228]
    28 322 ms 324 ms 338 ms sgp-2.valve.net [103.10.124.1]
    Last edited by Nyuucat; 12-17-2013 at 03:13 AM.

  6. #6
    Basic Member
    Join Date
    Dec 2013
    Posts
    30
    Quote Originally Posted by jupiter View Post
    Hi Nyuu cat, I feel very bad for you guys in SEA. This problem has happened for years and has resulted in low skilled SEA players invading my AUS servers.

    All I can say is launch cmd.exe and tracert the server, post it to the SEA server sticky and hope a dev sees it. Looking by the amount of pages that thread has, I certainly hope valve is working on a solution.

    Good luck and please don't join my server.
    Thank you jupiter and relax i won't be joining AUS Server. ^^

  7. #7
    Basic Member
    Join Date
    Nov 2013
    Posts
    15
    Hello, can u also looks on mine. i saw unusual high ping

    Tracing route to sgp-1.valve.net [103.28.54.1]
    over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 31 ms 27 ms 29 ms 36.76.176.1
    3 28 ms 55 ms 29 ms 180.252.0.57
    4 28 ms 31 ms 29 ms 61.94.115.209
    5 42 ms 43 ms 39 ms 118.98.63.241
    6 44 ms 47 ms 47 ms 118.98.15.241
    7 42 ms 37 ms 39 ms telkomnet.openixp.net [218.100.27.29]
    8 1652 ms 57 ms 1869 ms primenet.openixp.net [218.100.27.90]
    9 50 ms 51 ms 51 ms 103-28-54-221.valve.net [103.28.55.221]
    10 56 ms 55 ms 53 ms sgp-1.valve.net [103.28.54.1]
    Trace complete.

    Tracing route to sgp-2.valve.net [103.10.124.1]
    over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 29 ms 29 ms 27 ms 36.76.176.1
    3 30 ms 29 ms 29 ms 180.252.0.57
    4 50 ms 29 ms 29 ms 61.94.115.209
    5 42 ms 43 ms 43 ms 118.98.63.241
    6 46 ms 47 ms 47 ms 118.98.15.241
    7 38 ms 37 ms 39 ms telkomnet.openixp.net [218.100.27.29]
    8 488 ms 65 ms 57 ms primenet.openixp.net [218.100.27.90]
    9 52 ms 51 ms 51 ms 103-28-54-221.valve.net [103.28.55.221]
    10 53 ms 51 ms 51 ms 103.10.124.228
    11 53 ms 55 ms 57 ms sgp-2.valve.net [103.10.124.1]
    Trace complete.

    What does it mean with this unusual spikes...?

  8. #8
    Valve Developer
    Join Date
    Nov 2011
    Posts
    523
    This link is getting overloaded. I'll talk to the Primenet guys to see what they can do about it. I'll see if we can shed some more traffic off that path. We are waiting for an upgrade there.

  9. #9
    Basic Member
    Join Date
    Dec 2013
    Posts
    30
    Thank you ^^ , if and when u find a fix for it please inform us aswell.
    Last edited by Nyuucat; 12-18-2013 at 12:43 AM.

  10. #10
    Basic Member
    Join Date
    Nov 2013
    Posts
    15
    oh so thats what it's means, i got very low ping on game <80ms (still have some sudden lag but not often). kindda weird to see the trace goes up 1000ms ..

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •