RE: Routing Loops

Mailman List Mirror (Read Only)
1

Here is an example a Customer sent me. Sorry for the poor formating... trying to get from www.hyperchat.com to one of our dial up sites in Jacksonville, FL.

Sat Feb 08 19:19:06 bd3u *
seph said to Minnie:

     hi!.. *smile*.. it doesnt appear he is being blocked.. but..there
does appear to be a routing problem preventing
     him from getting here...

     Below is a trace which shows the problem. He needs to send this
trace to his provider...and ask them to followup
     and ask ANS to fix the problem... okay?

     Thanks...Seph

Tracing route to d00016.jax.bellsouth.net [207.53.14.17] over a maximum of 30 hops:
       1 10 ms 10 ms 10 ms usa-cisco.hyperchat.net[165.212.218.8]
       2 10 ms 10 ms 10 ms 165.212.231.1
       3 181 ms 120 ms 110 ms 192.156.196.252
       4 100 ms 100 ms 121 ms 192.103.71.33
       5 30 ms 50 ms 40 ms 140.222.96.221
       6 60 ms 71 ms 50 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
       7 * 90 ms 110 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
       8 80 ms 60 ms 50 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
       9 101 ms 90 ms 80 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
      10 70 ms 90 ms 91 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
      11 110 ms 160 ms 120 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
      12 120 ms 110 ms 100 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
      13 140 ms 130 ms 120 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
      14 171 ms 180 ms 150 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
      15 131 ms 150 ms 110 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
      16 120 ms 111 ms 130 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17]
      17 180 ms 130 ms 131 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14]
      18 130 ms 120 ms 120 ms

2

<list copied as a follow-up. Further discussion by me will be off-list.>

I would contact Gridnet's NOC to work with you and ANS' NOC to address the
issues. I am able to trace from the east coast to the address, bouncing the
trace off of ANS' Reston, VA router, but not from their San Francisco
router.

When it occurs again, you may want to go to http://nitros.digex.net and
look at how the route is being listened to by a provider (THANKS DIGEX FOR
A GREAT TOOL!).

+mike
network operations
INTERPATH

3

You missed a "u" - nitrous.digex.net.

:slight_smile:

DOH!!!

sorry about that. I hate being on the road and having to use this damn tiny
keyboard.

The proper URL is http://nitrous.digex.net