Mailing List Archive

routing loop in cogent?
Is anyone else seeing some routing loops in Cogent's network?

ala:

...
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475 ms 36.336 ms 34.087 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms 38.188 ms 37.530 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148 ms 37.066 ms 35.823 ms
21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms 37.534 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051 ms 33.120 ms 34.209 ms
23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603 ms 34.994 ms 34.119 ms
25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms 38.443 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784 ms 35.317 ms 33.839 ms
27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms 38.327 ms 39.863 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362 ms 36.451 ms 34.788 ms
29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms 39.782 ms 40.031 ms
30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156 ms 39.726 ms 35.726 ms
31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms 37.617 ms 49.460 ms
32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389 ms 35.988 ms 35.609 ms
33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms 121.744 ms^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20080623/7c75c278/attachment.html>
routing loop in cogent? [ In reply to ]
You should have kept the traceroute running. They might be passing
packets back and fourth a couple of dozen times as a practical joke
before eventually delivering the traffic to the next hop.

Cogent = WIN

On Jun 23, 2008, at 6:3911 000PM, Josh Fiske wrote:

> Is anyone else seeing some routing loops in Cogent's network?
>
> ala:
>
> ...
> 18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475
> ms 36.336 ms 34.087 ms
> 19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms
> 38.188 ms 37.530 ms
> 20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148
> ms 37.066 ms 35.823 ms
> 21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms
> 37.534 ms
> 22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051
> ms 33.120 ms 34.209 ms
> 23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
> 24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603
> ms 34.994 ms 34.119 ms
> 25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms
> 38.443 ms
> 26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784
> ms 35.317 ms 33.839 ms
> 27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms
> 38.327 ms 39.863 ms
> 28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362
> ms 36.451 ms 34.788 ms
> 29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms
> 39.782 ms 40.031 ms
> 30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156
> ms 39.726 ms 35.726 ms
> 31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms
> 37.617 ms 49.460 ms
> 32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389
> ms 35.988 ms 35.609 ms
> 33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms
> 121.744 ms^C
>
>
> - - - -
> Joshua Fiske '03, '04
> Network and Security Engineer
> Clarkson University, Office of Information Technology
> (315) 268-6722 -- Fax: (315) 268-6570
> GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
> jfiske at clarkson.edu
>
> CONFIDENTIALITY: This e-mail (including any attachments) may
> contain confidential, proprietary and privileged information, and
> unauthorized disclosure or use is prohibited. If you received this
> e-mail in error, please notify the sender and delete this e-mail
> from your system.
>
> _______________________________________________
> outages mailing list
> outages at isotf.org
> https://puck.nether.net/mailman/listinfo/outages
routing loop in cogent? [ In reply to ]
Also call USLEC, it seems it might be a problem on their side, because
it reaches cogent's uslec edge obviously.

On Jun 23, 2008, at 6:4317 000PM, Daniel Corbe wrote:

> You should have kept the traceroute running. They might be passing
> packets back and fourth a couple of dozen times as a practical joke
> before eventually delivering the traffic to the next hop.
>
> Cogent = WIN
>
> On Jun 23, 2008, at 6:3911 000PM, Josh Fiske wrote:
>
>> Is anyone else seeing some routing loops in Cogent's network?
>>
>> ala:
>>
>> ...
>> 18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475
>> ms 36.336 ms 34.087 ms
>> 19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms
>> 38.188 ms 37.530 ms
>> 20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148
>> ms 37.066 ms 35.823 ms
>> 21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms
>> 37.534 ms
>> 22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051
>> ms 33.120 ms 34.209 ms
>> 23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
>> 24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603
>> ms 34.994 ms 34.119 ms
>> 25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms
>> 38.443 ms
>> 26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784
>> ms 35.317 ms 33.839 ms
>> 27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms
>> 38.327 ms 39.863 ms
>> 28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362
>> ms 36.451 ms 34.788 ms
>> 29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms
>> 39.782 ms 40.031 ms
>> 30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156
>> ms 39.726 ms 35.726 ms
>> 31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms
>> 37.617 ms 49.460 ms
>> 32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389
>> ms 35.988 ms 35.609 ms
>> 33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms
>> 121.744 ms^C
>>
>>
>> - - - -
>> Joshua Fiske '03, '04
>> Network and Security Engineer
>> Clarkson University, Office of Information Technology
>> (315) 268-6722 -- Fax: (315) 268-6570
>> GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
>> jfiske at clarkson.edu
>>
>> CONFIDENTIALITY: This e-mail (including any attachments) may
>> contain confidential, proprietary and privileged information, and
>> unauthorized disclosure or use is prohibited. If you received this
>> e-mail in error, please notify the sender and delete this e-mail
>> from your system.
>>
>> _______________________________________________
>> outages mailing list
>> outages at isotf.org
>> https://puck.nether.net/mailman/listinfo/outages
>
routing loop in cogent? [ In reply to ]
Are you able to share what IP you're tracing to?
________________________________________
From: outages-bounces@isotf.org [outages-bounces@isotf.org] On Behalf Of Josh Fiske [jfiske@clarkson.edu]
Sent: Monday, June 23, 2008 9:39 PM
To: outages at isotf.org
Subject: [outages] routing loop in cogent?

Is anyone else seeing some routing loops in Cogent's network?

ala:

...
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475 ms 36.336 ms 34.087 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms 38.188 ms 37.530 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148 ms 37.066 ms 35.823 ms
21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms 37.534 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051 ms 33.120 ms 34.209 ms
23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603 ms 34.994 ms 34.119 ms
25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms 38.443 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784 ms 35.317 ms 33.839 ms
27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms 38.327 ms 39.863 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362 ms 36.451 ms 34.788 ms
29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms 39.782 ms 40.031 ms
30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156 ms 39.726 ms 35.726 ms
31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms 37.617 ms 49.460 ms
32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389 ms 35.988 ms 35.609 ms
33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms 121.744 ms^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.
routing loop in cogent? [ In reply to ]
On 23 Jun 2008, at 21:47, Darrell Hyde wrote:

> Are you able to share what IP you're tracing to?

I don't know much about cogent's naming scheme, but that traceroute
could be packets following a customer-announced aggregate and, lacking
a more-specific in the IGP, following a default back out to cogentland.


Joe
routing loop in cogent? [ In reply to ]
Complete traceroute for the interested... (FWIW, 205.232.34.1 is the DNS for a small ISP in central NY.) At this point, I cannot determine whether they have dropped off the map or whether Cogent is just mis-routing traffic...I don't have another host on the other side of Cogent's cloud to trace to.

$ traceroute 205.232.34.1
traceroute to 205.232.34.1 (205.232.34.1), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.205 ms 0.899 ms 0.744 ms
2 10.101.32.1 (10.101.32.1) 9.872 ms 12.886 ms 8.218 ms
3 gig0-0.syrcnypth-rtr01.nyroc.rr.com (24.92.227.102) 8.842 ms 7.082 ms 7.968 ms
4 gig6-3.syrcnypth-rtr02.nyroc.rr.com (24.92.230.74) 8.523 ms 8.358 ms 22.373 ms
5 gig1-0-7.syrcnyflk-rtr02.nyroc.rr.com (24.92.227.42) 12.746 ms 12.645 ms 13.085 ms
6 * ge-4-3-0.albynywav-rtr03.nyroc.rr.com (24.24.7.53) 22.296 ms 23.362 ms
7 ae-5-0.cr0.nyc30.tbone.rr.com (66.109.6.74) 24.973 ms 25.460 ms 25.236 ms
8 ae-1-0.pr0.nyc20.tbone.rr.com (66.109.6.163) 26.920 ms 27.645 ms 28.417 ms
9 te2-1.mpd01.jfk05.atlas.cogentco.com (154.54.13.185) 27.786 ms 28.297 ms 28.696 ms
10 vl3496.mpd03.jfk02.atlas.cogentco.com (154.54.6.49) 28.706 ms vl3491.ccr04.jfk02.atlas.cogentco.com (154.54.7.9) 29.195 ms vl3496.mpd03.jfk02.atlas.cogentco.com (154.54.6.49) 30.475 ms
11 te4-1.ccr01.jfk07.atlas.cogentco.com (154.54.7.30) 28.199 ms 27.434 ms 28.647 ms
12 paetec_communications_inc.dmarc.cogentco.com (38.112.26.90) 29.272 ms 30.293 ms 28.723 ms
13 gi-1-0-1-13.core01.nycmny01.paetec.net (66.155.218.97) 28.767 ms 30.290 ms 29.108 ms
14 64.80.253.234 (64.80.253.234) 27.571 ms 29.827 ms 28.415 ms
15 ge-1-3-0.core02.nycmny03.paetec.net (64.80.253.98) 29.724 ms 27.800 ms 28.632 ms
16 as1.core02.asbnva01.paetec.net (169.130.81.230) 37.043 ms 44.398 ms 86.877 ms
17 so-0-1-0.core01.asbnva01.paetec.net (169.130.81.85) 36.541 ms 36.753 ms 35.901 ms
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.438 ms 34.282 ms 33.746 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.553 ms 35.728 ms 38.174 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.176 ms 33.785 ms 33.844 ms
21 uslec.iad01.atlas.cogentco.com (154.54.11.214) 102.015 ms 37.123 ms 37.943 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.138 ms 34.589 ms 34.388 ms
23 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.982 ms 37.857 ms
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 36.449 ms 35.107 ms 34.794 ms
25 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.972 ms 36.947 ms 38.100 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.736 ms 33.483 ms *
27 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.605 ms 37.762 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 37.073 ms 34.558 ms 36.043 ms
29 *^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.



-----Original Message-----
From: outages-bounces@isotf.org on behalf of Darrell Hyde
Sent: Mon 6/23/2008 9:47 PM
To: outages at isotf.org
Subject: Re: [outages] routing loop in cogent?

Are you able to share what IP you're tracing to?
________________________________________
From: outages-bounces@isotf.org [outages-bounces@isotf.org] On Behalf Of Josh Fiske [jfiske@clarkson.edu]
Sent: Monday, June 23, 2008 9:39 PM
To: outages at isotf.org
Subject: [outages] routing loop in cogent?

Is anyone else seeing some routing loops in Cogent's network?

ala:

...
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475 ms 36.336 ms 34.087 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms 38.188 ms 37.530 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148 ms 37.066 ms 35.823 ms
21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms 37.534 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051 ms 33.120 ms 34.209 ms
23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603 ms 34.994 ms 34.119 ms
25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms 38.443 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784 ms 35.317 ms 33.839 ms
27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms 38.327 ms 39.863 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362 ms 36.451 ms 34.788 ms
29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms 39.782 ms 40.031 ms
30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156 ms 39.726 ms 35.726 ms
31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms 37.617 ms 49.460 ms
32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389 ms 35.988 ms 35.609 ms
33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms 121.744 ms^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.


_______________________________________________
outages mailing list
outages at isotf.org
https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20080623/d847d193/attachment.html>
routing loop in cogent? [ In reply to ]
On Mon, Jun 23, 2008 at 10:03:39PM -0400, Josh Fiske wrote:
> Complete traceroute for the interested... (FWIW, 205.232.34.1 is the DNS for a small ISP in central NY.) At this point, I cannot determine whether they have dropped off the map or whether Cogent is just mis-routing traffic...I don't have another host on the other side of Cogent's cloud to trace to.

FWIW, I see the same thing from a different source (72.20.106.2):

traceroute to 205.232.34.1 (205.232.34.1), 64 hops max, 40 byte packets
1 72.20.106.1 (72.20.106.1) 0.617 ms 0.612 ms 0.407 ms
2 er0sc1-g2-0.bayarea.net (209.128.116.90) 0.395 ms 0.283 ms 0.239 ms
3 er0sc1-g2-1.BAYAREA.NET (209.128.95.91) 0.398 ms 0.290 ms 0.240 ms
4 ge-7-19.car1.SanJose1.Level3.net (4.79.219.105) 6.478 ms 1.069 ms 0.864 ms
5 vlan69.csw1.SanJose1.Level3.net (4.68.18.62) 12.565 ms 1.067 ms 0.865 ms
6 ae-64-64.ebr4.SanJose1.Level3.net (4.69.134.241) 5.855 ms 8.256 ms 1.335 ms
7 ae-2.ebr4.NewYork1.Level3.net (4.69.135.186) 120.723 ms 121.408 ms 127.543 ms
8 ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) 124.579 ms 126.670 ms 126.923 ms
9 ae-21-79.car1.NewYork1.Level3.net (4.68.16.67) 80.583 ms
ae-31-89.car1.NewYork1.Level3.net (4.68.16.131) 80.788 ms 80.472 ms
10 unknown.Level3.net (63.208.174.2) 135.902 ms 129.309 ms 126.605 ms
11 as1.core02.asbnva01.paetec.net (169.130.81.230) 80.898 ms 80.953 ms 81.211 ms
12 so-0-1-0.core01.asbnva01.paetec.net (169.130.81.85) 80.587 ms 80.496 ms 80.741 ms
13 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 80.585 ms 80.604 ms 80.744 ms
14 uslec.iad01.atlas.cogentco.com (154.54.11.214) 81.052 ms 80.858 ms 80.914 ms
15 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 80.936 ms 80.741 ms 80.902 ms
16 * * uslec.iad01.atlas.cogentco.com (154.54.11.214) 81.039 ms
17 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 81.092 ms 80.618 ms 80.787 ms
18 uslec.iad01.atlas.cogentco.com (154.54.11.214) 80.897 ms 81.551 ms 81.051 ms
19 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 81.050 ms 81.082 ms 81.523 ms
20 * * *
21 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 81.833 ms 81.716 ms 81.744 ms
22 uslec.iad01.atlas.cogentco.com (154.54.11.214) 81.564 ms 81.462 ms 81.992 ms
23 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 81.364 ms 81.866 ms 82.318 ms
^C

--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
routing loop in cogent? [ In reply to ]
Josh Fiske wrote:
> Complete traceroute for the interested... (FWIW, 205.232.34.1 is the
> DNS for a small ISP in central NY.) At this point, I cannot determine
> whether they have dropped off the map or whether Cogent is just
> mis-routing traffic...I don't have another host on the other side of
> Cogent's cloud to trace to.

It's reachable from here, but not through Cogent.


3 f0-0.border2.sba1.netlojix.net (207.71.192.51) 41.404 ms 323.870
ms 330.528 ms
4 so-1-0.ipcolo1.losangeles1.level3.net (64.156.173.57) 36.368 ms
39.335 ms 34.199 ms
5 vlan51.csw1.losangeles1.level3.net (4.68.102.30) 35.790 ms 37.564
ms 38.921 ms
6 ae-14-69.car4.losangeles1.level3.net (4.68.20.6) 37.759 ms 36.463
ms 39.010 ms
7 globalcrossing-level3-10ge.losangeles1.level3.net (4.68.110.66)
41.986 ms 43.080 ms 35.000 ms
8 64.209.107.158 (64.209.107.158) 118.865 ms 123.881 ms 120.093 ms
9 66.152.112.10 (66.152.112.10) 121.595 ms 119.958 ms 121.811 ms
10 66.152.113.44 (66.152.113.44) 123.470 ms 122.608 ms 122.927 ms
11 bond0b.lightlink.com (216.7.9.33) 130.447 ms 128.141 ms 131.083 ms
12 fw1.lightlink.com (205.232.89.2) 142.068 ms 139.863 ms 139.027 ms
13 205.232.34.1.lightlink.com (205.232.34.1) 129.275 ms 137.171 ms
149.257 ms

--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
Impulse Internet Service - http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV
routing loop in cogent? [ In reply to ]
Might helpful to call the ISP (http://www.lightlink.com/light.html) and ask
the person to trace back to you and see if they seem the same thing.



If 205.232.34.1 is their DNS server, it doesn't match what's in the DNS for
lightlink.com. They also might considering renaming the reverse for this
DNS server to something that makes a bit more sense than
205.232.34.1.lightlink.com.



Frank



From: outages-bounces@isotf.org [mailto:outages-bounces@isotf.org] On Behalf
Of Josh Fiske
Sent: Monday, June 23, 2008 9:04 PM
To: Darrell Hyde; outages at isotf.org
Subject: Re: [outages] routing loop in cogent?



Complete traceroute for the interested... (FWIW, 205.232.34.1 is the DNS
for a small ISP in central NY.) At this point, I cannot determine whether
they have dropped off the map or whether Cogent is just mis-routing
traffic...I don't have another host on the other side of Cogent's cloud to
trace to.

$ traceroute 205.232.34.1
traceroute to 205.232.34.1 (205.232.34.1), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.205 ms 0.899 ms 0.744 ms
2 10.101.32.1 (10.101.32.1) 9.872 ms 12.886 ms 8.218 ms
3 gig0-0.syrcnypth-rtr01.nyroc.rr.com (24.92.227.102) 8.842 ms 7.082 ms
7.968 ms
4 gig6-3.syrcnypth-rtr02.nyroc.rr.com (24.92.230.74) 8.523 ms 8.358 ms
22.373 ms
5 gig1-0-7.syrcnyflk-rtr02.nyroc.rr.com (24.92.227.42) 12.746 ms 12.645
ms 13.085 ms
6 * ge-4-3-0.albynywav-rtr03.nyroc.rr.com (24.24.7.53) 22.296 ms 23.362
ms
7 ae-5-0.cr0.nyc30.tbone.rr.com (66.109.6.74) 24.973 ms 25.460 ms
25.236 ms
8 ae-1-0.pr0.nyc20.tbone.rr.com (66.109.6.163) 26.920 ms 27.645 ms
28.417 ms
9 te2-1.mpd01.jfk05.atlas.cogentco.com (154.54.13.185) 27.786 ms 28.297
ms 28.696 ms
10 vl3496.mpd03.jfk02.atlas.cogentco.com (154.54.6.49) 28.706 ms
vl3491.ccr04.jfk02.atlas.cogentco.com (154.54.7.9) 29.195 ms
vl3496.mpd03.jfk02.atlas.cogentco.com (154.54.6.49) 30.475 ms
11 te4-1.ccr01.jfk07.atlas.cogentco.com (154.54.7.30) 28.199 ms 27.434 ms
28.647 ms
12 paetec_communications_inc.dmarc.cogentco.com (38.112.26.90) 29.272 ms
30.293 ms 28.723 ms
13 gi-1-0-1-13.core01.nycmny01.paetec.net (66.155.218.97) 28.767 ms
30.290 ms 29.108 ms
14 64.80.253.234 (64.80.253.234) 27.571 ms 29.827 ms 28.415 ms
15 ge-1-3-0.core02.nycmny03.paetec.net (64.80.253.98) 29.724 ms 27.800 ms
28.632 ms
16 as1.core02.asbnva01.paetec.net (169.130.81.230) 37.043 ms 44.398 ms
86.877 ms
17 so-0-1-0.core01.asbnva01.paetec.net (169.130.81.85) 36.541 ms 36.753
ms 35.901 ms
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.438 ms 34.282
ms 33.746 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.553 ms 35.728 ms
38.174 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.176 ms 33.785
ms 33.844 ms
21 uslec.iad01.atlas.cogentco.com (154.54.11.214) 102.015 ms 37.123 ms
37.943 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.138 ms 34.589
ms 34.388 ms
23 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.982 ms 37.857 ms
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 36.449 ms 35.107
ms 34.794 ms
25 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.972 ms 36.947 ms
38.100 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.736 ms 33.483
ms *
27 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.605 ms 37.762 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 37.073 ms 34.558
ms 36.043 ms
29 *^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this e-mail in error,
please notify the sender and delete this e-mail from your system.



-----Original Message-----
From: outages-bounces@isotf.org on behalf of Darrell Hyde
Sent: Mon 6/23/2008 9:47 PM
To: outages at isotf.org
Subject: Re: [outages] routing loop in cogent?

Are you able to share what IP you're tracing to?
________________________________________
From: outages-bounces@isotf.org [outages-bounces@isotf.org] On Behalf Of
Josh Fiske [jfiske at clarkson.edu]
Sent: Monday, June 23, 2008 9:39 PM
To: outages at isotf.org
Subject: [outages] routing loop in cogent?

Is anyone else seeing some routing loops in Cogent's network?

ala:

...
18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475 ms 36.336
ms 34.087 ms
19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms 38.188 ms
37.530 ms
20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148 ms 37.066
ms 35.823 ms
21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms 37.534 ms
22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051 ms 33.120
ms 34.209 ms
23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * *
24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603 ms 34.994
ms 34.119 ms
25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms 38.443 ms
26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784 ms 35.317
ms 33.839 ms
27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms 38.327 ms
39.863 ms
28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362 ms 36.451
ms 34.788 ms
29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms 39.782 ms
40.031 ms
30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156 ms 39.726
ms 35.726 ms
31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms 37.617 ms
49.460 ms
32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389 ms 35.988
ms 35.609 ms
33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms 121.744 ms^C


- - - -
Joshua Fiske '03, '04
Network and Security Engineer
Clarkson University, Office of Information Technology
(315) 268-6722 -- Fax: (315) 268-6570
GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc
jfiske at clarkson.edu

CONFIDENTIALITY: This e-mail (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this e-mail in error,
please notify the sender and delete this e-mail from your system.


_______________________________________________
outages mailing list
outages at isotf.org
https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20080623/7c1cb9fb/attachment-0001.html>