Announcement

Collapse
No announcement yet.

How does one go about correcting a route to a host?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • How does one go about correcting a route to a host?

    Hello.

    Recently the TG team provisioned a new BF4 server in Chicago. My ping to this new server has gone from 40 -> 150.

    Looking at traceroute the problem begins in hop 12:

    Tracing route to host.colocrossing.com [199.21.113.219]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.2.1]
    2 17 ms 17 ms 9 ms cpe-104-138-160-1.triad.res.rr.com [104.138.160.1]
    3 43 ms 37 ms 38 ms cpe-174-111-126-097.triad.res.rr.com [174.111.126.97]
    4 18 ms 20 ms 16 ms cpe-024-028-255-064.triad.res.rr.com [24.28.255.64]
    5 19 ms 22 ms 24 ms be34.drhmncev01r.southeast.rr.com [24.93.64.196]
    6 26 ms 27 ms 28 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
    7 26 ms 28 ms 48 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
    8 27 ms 25 ms 38 ms 209.48.42.213
    9 27 ms 37 ms 27 ms 207.88.14.180.ptr.us.xo.net [207.88.14.180]
    10 29 ms 24 ms 22 ms 207.88.14.191.ptr.us.xo.net [207.88.14.191]
    11 29 ms 26 ms 22 ms ae30.was14.ip4.gtt.net [173.205.55.117]
    12 162 ms 182 ms 179 ms xe-3-1-2.chi18.ip4.gtt.net [141.136.108.242]
    13 169 ms 174 ms 166 ms servercentral-gw.ip4.gtt.net [173.205.55.130]
    14 199 ms 178 ms 175 ms servers.fragnet.net [206.217.136.98]
    15 186 ms 180 ms 189 ms host.colocrossing.com [199.21.113.219]

    Trace complete.


    The output of visual traceroute is very interesting:

    #, Country, Town, Lat, Lon, IP, Hostname, Latency (ms), DNS Lookup (ms), Distance to previous node (km), Whois
    1, United States, Clemmons, 36.007904, -80.3697, 192.168.2.1, pfSense.localdomain, 4, 46, 0, 192.168.2.1
    2, United States, Clemmons, 36.007904, -80.3697, 104.138.160.1, cpe-104-138-160-1.triad.res.rr.com, 36, 1, 0, 104.138.160.1
    3, United States, (Unknown), 37.751007, -97.822, 174.111.126.97, cpe-174-111-126-097.triad.res.rr.com, 64, 1, 1563, 174.111.126.97
    4, United States, (Unknown), 37.751007, -97.822, 24.28.255.64, cpe-024-028-255-064.triad.res.rr.com, 25, 1, 0, 24.28.255.64
    5, United States, (Unknown), 37.751007, -97.822, 24.93.64.196, be34.drhmncev01r.southeast.rr.com, 25, 1, 0, 24.93.64.196
    6, United States, (Unknown), 37.751007, -97.822, 66.109.6.80, bu-ether15.asbnva1611w-bcr00.tbone.rr.com, 49, 1, 0, 66.109.6.80
    7, United States, (Unknown), 37.751007, -97.822, 107.14.17.204, 0.ae2.pr1.dca10.tbone.rr.com, 36, 1, 0, 107.14.17.204
    8, United States, (Unknown), 37.751007, -97.822, 209.48.42.213, (None), 36, 1, 0, 209.48.42.213
    9, United States, (Unknown), 37.751007, -97.822, 207.88.14.180, 207.88.14.180.ptr.us.xo.net, 49, 1, 0, 207.88.14.180
    10, United States, (Unknown), 37.751007, -97.822, 207.88.14.191, 207.88.14.191.ptr.us.xo.net, 49, 1, 0, 207.88.14.191
    11, United States, (Unknown), 37.751007, -97.822, 173.205.55.117, ae30.was14.ip4.gtt.net, 49, 1, 0, 173.205.55.117
    12, France, (Unknown), 48.8582, 2.3386993, 141.136.108.242, xe-3-1-2.chi18.ip4.gtt.net, 36, 1, 7606, 141.136.108.242
    13, United States, (Unknown), 37.751007, -97.822, 173.205.55.130, servercentral-gw.ip4.gtt.net, 49, 2, 7606, 173.205.55.130
    14, United States, Buffalo, 42.986404, -78.7279, 206.217.136.98, servers.fragnet.net, 64, 1, 1716, 206.217.136.98
    15, United States, Chicago, 41.850006, -87.65, 199.21.113.219, host.colocrossing.com, 49, 2, 743, 199.21.113.219


    Turns out hop 12 is France! My traffic is bouncing to France and back before continuing onward.

    Who the hell would I contact to try and get this corrected? Do I start with my ISP (TWC)? Do I try and contact gtt?

    Any help and suggestions would be greatly appreciated.

  • #2
    Re: How does one go about correcting a route to a host?

    There's really not much you can do. You COULD find a support contact for gtt.net and send them an email asking what's up, but don't assume that it's something that's "wrong" or "broken" without talking to them first. The Internet is a dynamic beast with routing protocols DESIGNED to route around network drops, and congested nodes. If there was a fiber cut on the preferred hop between nodes #11 and #13, and nodes #11 and #13 had connectivity through France, it very well may be the shortest on-network hop between the nodes. The alternative to routing traffic through France could have been full disconnection between the networks vs. a long distance hop.

    Additionally, it could have been a mistake made by an ISP in France where they accidentally announced routes they shouldn't have and are taking over GTT's traffic. Those types of issues are usually corrected quickly as the ISP that makes the mistake will suddenly find themselves routing ENORMOUS traffic over THEIR network that they don't want, need or can handle.

    Run the traces again today and see if they change. If not, go the GTT contact route as your ISP really has no control over how GTT routes it's traffic.

    +1 extra points for using pfSense.
    Diplomacy is the art of saying "good doggie" while looking for a bigger stick.

    Comment


    • #3
      Re: How does one go about correcting a route to a host?

      Originally posted by Apophis View Post
      Run the traces again today and see if they change. If not, go the GTT contact route as your ISP really has no control over how GTT routes it's traffic.
      Already done. I've been running these traces a couple of times a day over the last three days without change. I will try and dig up a public contact at GTT and ask them if they could look into it.

      Originally posted by Apophis View Post
      +1 extra points for using pfSense.
      I've been using pfSense for about 4 years now. Best routing solution I've ever had. Very flexible.

      Comment


      • #4
        Re: How does one go about correcting a route to a host?

        I emailed GTT's NOC. I got a reply within 5 minutes. Turns out the geo location of hop 12 is actually in Chicago (hence the chi in its host name). No explanation for the latency. Interestingly, though, about 5 minutes after that reply my ping time on that hop dropped to 50ms. This is the first time since noticing the problem that it has dropped. It could be a coincidence due to time of day, traffic, etc. I think I'm going to setup a script to gather ping times once per minute over a 72 hour period and see if there is any correlation to time of day.

        Comment


        • #5
          Re: How does one go about correcting a route to a host?

          I was going to mention potential geoip issues in my last response as when I was pulling geoip data for that IP it was showing up as being in Germany for me. Quite the coincidence on the geoip error AND the huge increase in ping both on the same node...
          Diplomacy is the art of saying "good doggie" while looking for a bigger stick.

          Comment


          • #6
            Re: How does one go about correcting a route to a host?

            Well it was too good to be true.

            As the 5'oclock hour wore on, the ping got worse. Now the ping is back to the 120+ arena. At the moment it appears to correlate to time of day.

            If this persists, my time on the TG BF4 server may be coming to an end.

            Comment


            • #7
              Re: How does one go about correcting a route to a host?

              You were playing over the weekend...any improvement?


              Sent from my iPhone using Tapatalk
              |TG|Melee
              Clear Eyes, Full Hearts, Can't Lose!

              Comment


              • #8
                Re: How does one go about correcting a route to a host?

                Friday night I exchanged another 2 emails with their NOC support address. I never got any confirmation that they would look into it, but Saturday & Sunday night my ping was 40-60 even with glray3 playing as well. As of right now its still holding.

                Comment


                • #9
                  Re: How does one go about correcting a route to a host?

                  Looks like I am affected by this as well :(

                  Microsoft Windows [Version 10.0.10586]
                  (c) 2015 Microsoft Corporation. All rights reserved.

                  C:\Users\Reaper>ping 199.21.113.219

                  Pinging 199.21.113.219 with 32 bytes of data:
                  Reply from 199.21.113.219: bytes=32 time=174ms TTL=110
                  Reply from 199.21.113.219: bytes=32 time=163ms TTL=110
                  Reply from 199.21.113.219: bytes=32 time=171ms TTL=110
                  Reply from 199.21.113.219: bytes=32 time=171ms TTL=110

                  Ping statistics for 199.21.113.219:
                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                  Approximate round trip times in milli-seconds:
                  Minimum = 163ms, Maximum = 174ms, Average = 169ms

                  C:\Users\Reaper>tracert 199.21.113.219

                  Tracing route to host.colocrossing.com [199.21.113.219]
                  over a maximum of 30 hops:

                  1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
                  2 16 ms 15 ms 11 ms 10.197.160.1
                  3 17 ms 18 ms 23 ms 72-31-218-126.net.bhntampa.com [72.31.218.126]
                  4 17 ms 19 ms 18 ms ten0-0-0-3.orld31-car1.bhn.net [72.31.188.148]
                  5 22 ms 19 ms 20 ms 72-31-220-148.net.bhntampa.com [72.31.220.148]
                  6 21 ms 18 ms 18 ms 72-31-188-172.net.bhntampa.com [72.31.188.172]
                  7 24 ms 19 ms 19 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
                  8 37 ms * 27 ms 0.ae1.pr0.mia00.tbone.rr.com [66.109.1.87]
                  9 56 ms 51 ms 49 ms ix-ae-23-0.tcore1.MLN-Miami.as6453.net [63.243.152.105]
                  10 47 ms 50 ms 49 ms if-ae-1-2.tcore2.MLN-Miami.as6453.net [63.243.152.62]
                  11 51 ms 49 ms 49 ms 66.110.9.166
                  12 70 ms 69 ms 68 ms xe-7-3-0.chi18.ip4.gtt.net [141.136.107.242]
                  13 86 ms 69 ms 70 ms servercentral-gw.ip4.gtt.net [173.205.55.134]
                  14 93 ms * 85 ms servers.fragnet.net [206.217.136.98]
                  15 179 ms 173 ms 171 ms host.colocrossing.com [199.21.113.219]

                  Trace complete.

                  C:\Users\Reaper>

                  Will be seeing if its just the time of day, I was fine Friday though :/

                  Comment


                  • #10
                    Re: How does one go about correcting a route to a host?

                    [MENTION=103085]US_GrimReaper[/MENTION] does this look familiar?

                    Tracing route to host.colocrossing.com [199.21.113.219]
                    over a maximum of 30 hops:

                    1 <1 ms <1 ms <1 ms pfSense.draeh.org [192.168.2.1]
                    2 17 ms 21 ms 20 ms cpe-104-138-160-1.triad.res.rr.com [104.138.160.1]
                    3 40 ms 33 ms 31 ms cpe-174-111-126-161.triad.res.rr.com [174.111.126.161]
                    4 16 ms 16 ms 20 ms cpe-024-028-255-064.triad.res.rr.com [24.28.255.64]
                    5 21 ms 23 ms 24 ms be34.drhmncev01r.southeast.rr.com [24.93.64.196]
                    6 56 ms 37 ms 73 ms bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
                    7 35 ms 30 ms 24 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
                    8 29 ms 29 ms 19 ms 209.48.42.213
                    9 36 ms 28 ms 26 ms 207.88.14.180.ptr.us.xo.net [207.88.14.180]
                    10 25 ms 29 ms 34 ms 207.88.14.191.ptr.us.xo.net [207.88.14.191]
                    11 35 ms 44 ms 44 ms ae30.was14.ip4.gtt.net [173.205.55.117]
                    12 55 ms 54 ms 50 ms xe-10-0-6.chi18.ip4.gtt.net [141.136.106.166]
                    13 60 ms 57 ms 61 ms servercentral-gw.ip4.gtt.net [173.205.55.130]
                    14 71 ms 69 ms 70 ms servers.fragnet.net [206.217.136.98]
                    15 135 ms 150 ms 150 ms host.colocrossing.com [199.21.113.219]

                    Trace complete.


                    Fixed my one routing issue to be hit with another... except this time its the server provider themselves?


                    It was a nice couple of weeks while it lasted.

                    Comment


                    • #11
                      Re: How does one go about correcting a route to a host?

                      :( very familiar... although last night.... i had a ping of 70!

                      Comment

                      Connect

                      Collapse

                      TeamSpeak 3 Server

                      Collapse

                      Advertisement

                      Collapse

                      Twitter Feed

                      Collapse

                      Working...
                      X