Results 1 to 9 of 9
  1. #1
    Join Date
    Jan 2005
    Posts
    2,166

    * Routing problem with Gblx or Level3 ?

    I'm located in New York, the box is in Tampa Bay, Florida.

    The route starts from Tampa Bay Gblx -> Dallas Gblx -> Dallas Level3 -> Atlanta Level3 -> Washington Level3 -> Newark Level3 -> ISP routers

    Packet is traveling from southeast to northwest then back to northeast. WTF is going on? It used to go from Tampa Bay Gblx to Newark Level3 then to my ISP routers.

    3 ge-3-0-0.ar2.TPA1.gblx.net (64.214.175.193) 0.657 ms 0.634 ms 0.610 ms
    4 por4-0-0-10G.ar2.DAL2.gblx.net (67.17.105.38) 25.627 ms 25.503 ms 25.572 ms
    5 64.208.110.206 (64.208.110.206) 25.473 ms 25.344 ms 25.441 ms
    6 ae-31-53.ebr1.Dallas1.Level3.net (4.68.122.94) 27.093 ms ae-31-51.ebr1.Dallas1.Level3.net (4.68.122.30) 26.326 ms ae-31-55.ebr1.Dallas1.Level3.net (4.68.122.158) 36.549 ms
    7 ae-1-100.ebr1.Dallas1.Level3.net (4.69.132.45) 39.201 ms ae-3.ebr1.Atlanta2.Level3.net (4.69.132.82) 45.552 ms 43.950 ms
    8 ae-2.ebr1.Washington1.Level3.net (4.69.132.86) 55.545 ms ae-3.ebr1.Atlanta2.Level3.net (4.69.132.82) 43.712 ms ae-2.ebr1.Washington1.Level3.net (4.69.132.86) 51.848 ms
    9 ae-1-100.ebr2.Washington1.Level3.net (4.69.132.30) 51.296 ms ae-2.ebr1.Washington1.Level3.net (4.69.132.86) 45.695 ms ae-1-100.ebr2.Washington1.Level3.net (4.69.132.30) 51.324 ms
    10 ae-4.ebr2.Newark1.Level3.net (4.69.132.102) 52.564 ms 61.197 ms 72.794 ms
    11 ae-21-52.car1.Newark1.Level3.net (4.68.99.37) 52.574 ms ae-4.ebr2.Newark1.Level3.net (4.69.132.102) 59.774 ms ae-21-56.car1.Newark1.Level3.net (4.68.99.165) 51.819 ms
    12 ROADRUNNER.car1.Newark1.Level3.net (4.79.188.114) 52.270 ms 4.79.188.34 (4.79.188.34) 51.926 ms 4.79.188.38 (4.79.188.38) 52.641 ms
    13 ROADRUNNER.car1.Newark1.Level3.net (4.79.188.114) 52.406 ms tenge-5-0-0.nycsnyoo-rtr1.nyc.rr.com (24.29.119.165) 52.581 ms 52.171 ms
    14 tenge3-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.113) 52.044 ms tenge-5-0-0.nycsnyoo-rtr1.nyc.rr.com (24.29.119.165) 52.027 ms tenge3-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.113) 52.563 ms
    15 pos2-0-nycmnyd-rtr1.nyc.rr.com (24.29.97.37) 52.803 ms tenge3-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.113) 52.782 ms pos2-0-nycmnyd-rtr1.nyc.rr.com (24.29.97.37) 52.970 ms
    16 pos2-0-nycmnyd-rtr1.nyc.rr.com (24.29.97.37) 52.665 ms pos3-0-nycmnyd-rtr2.nyc.rr.com (24.29.101.214) 51.937 ms 52.420 ms
    17 pos1-0-nycmnyd-ubr4.nyc.rr.com (24.29.100.146) 52.925 ms 53.001 ms pos3-0-nycmnyd-rtr2.nyc.rr.com (24.29.101.214) 53.540 ms
    Edit: why are some hops showing more than one IP?
    Last edited by HD Fanatic; 02-23-2007 at 02:50 PM.

  2. #2
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,547
    That is not a routing problem. The "closest exit" is likely Dallas. In other words, it is probably the nearest peering point with Level(3) for GBLX.

  3. #3
    Join Date
    Jan 2005
    Posts
    2,166
    That's terrible then it goes to Washington... gblx has very bad peering with level3.

  4. #4
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,547
    Quote Originally Posted by ANewDay
    That's terrible then it goes to Washington... gblx has very bad peering with level3.
    AFAIK GBLX did not have peering with Level(3) in Dallas until recently, therefore the "closest exit" before may have been Washington, DC until they implemented the new peering location w/ L3. While this may be an inefficient route for your case, its not so bad for westbound traffic. Tampa isn't a tier-1 city IIRC, therefore I would not expect there to be much if any local peering. It is unfair to fault GBLX in that respect.

  5. #5
    Join Date
    Jan 2005
    Posts
    2,166
    Gblx used to peer with Level(3) in Newark, New Jersey. btw, it's Washington, not Washington DC

  6. #6
    Join Date
    Nov 2005
    Location
    Minneapolis, MN
    Posts
    1,646
    It very much is Wash DC. You can't make it to the west coast and back with the latency numbers you've posted.
    Eric Spaeth
    Enterprise Network Engineer :: Hosting Hobbyist :: Master of Procrastination
    "The really cool thing about facts is they remain true regardless of who states them." -SpaethCo

  7. #7
    Join Date
    Dec 2004
    Location
    New York, NY
    Posts
    10,547
    Quote Originally Posted by ANewDay
    Gblx used to peer with Level(3) in Newark, New Jersey. btw, it's Washington, not Washington DC
    GBLX still is peered with L3 in that area:

    1 64.214.13.1 (64.214.13.1) 3.274 ms 0.391 ms
    2 ge4-1-10G.ar4.NYC1.gblx.net (67.17.104.190) 0.672 ms 0.871 ms
    3 ge-6-21.car4.NewYork1.Level3.net (4.68.111.237) 0.901 ms 0.684 ms

    However, that is irrelevant to the discussion. While it may be doing this for your inbound route, as naturally it is the "closest exit" for L3, it was probably never doing this for the outbound route. Most routes from Florida tend to go through Dallas or North Virginia / Washington, DC. A good amount also go through Atlanta, GA.

  8. #8
    Join Date
    Feb 2002
    Location
    New York, NY
    Posts
    4,552
    I don't see any problems with this route. Tampa is not a tier 1 city, so it is quite reasonable to see packets go through Dallas first. The rest of the hops after Dallas follow a natural path to NYC. It's going from Tampa to Dallas, to WDC (or Atlanta in some packets), to Newark, then to New York City. Seems like a normal route.

    To answer your other question, you are seeing multiple routers on some hops because the packets aren't all going over the same route. Also, as Eric pointed out, that Washington hop is Washington, DC, and not the state of Washington.
    Scott Burns, President
    BQ Internet Corporation
    Remote Rsync and FTP backup solutions
    *** http://www.bqbackup.com/ ***

  9. #9
    Join Date
    Jan 2005
    Posts
    2,166
    I see, when it was usng level3 or gblx, it didn't go through Dallas though. It went straight to New Jersey from Tampa. I don't know what changed recently.

Posting Permissions

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