On Mon, Jan 22, 2001 at 03:05:20AM -0500, Joe Budion wrote:
This one takes the cake for weirdest route I've ever seen:
10 p9-0.crtntx1-br1.bbnplanet.net (4.24.10.213) 48 msec 48 msec 44 msec 11 p15-0.crtntx1-br2.bbnplanet.net (4.24.10.114) 48 msec 48 msec 48 msec 12 p2-0.crtntx1-cr8.bbnplanet.net (4.24.8.198) 48 msec 48 msec 48 msec 13 p5-0.toucham.bbnplanet.net (4.24.117.66) 68 msec 68 msec 68 msec 14 den-edge-18.inet.qwest.net (205.171.16.34) 68 msec 68 msec 68 msec 15 208.46.255.14 120 msec 120 msec 120 msec 16 63.237.115.200 120 msec 120 msec 120 msec ner-routes>sh ip bgp 205.171.16.34 BGP routing table entry for 205.171.16.32/30, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 0, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58 ner-routes>sh ip bgp 63.237.115.20 BGP routing table entry for 63.237.115.0/27, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 5, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58 Gotte filters? -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
The part that I was particularly concerned about was where it left qwest for BBNPlanet and got right back on Qwest. I went ahead and gave them a call (at the number listed on Jared's page), and they asked for a traceroute, etc. I gave them all the research that I had done and they just kinda fell silent when they saw my email to them. Then they said "We'll have our NOC group take a look at this.". I thought that I had called the NOC!!!! Yet more examples of clueless morons manning the phones. (Not saying that my employer is not guilty of the same :-( ), On Mon, 22 Jan 2001, Richard A. Steenbergen wrote:
On Mon, Jan 22, 2001 at 03:05:20AM -0500, Joe Budion wrote:
This one takes the cake for weirdest route I've ever seen:
10 p9-0.crtntx1-br1.bbnplanet.net (4.24.10.213) 48 msec 48 msec 44 msec 11 p15-0.crtntx1-br2.bbnplanet.net (4.24.10.114) 48 msec 48 msec 48 msec 12 p2-0.crtntx1-cr8.bbnplanet.net (4.24.8.198) 48 msec 48 msec 48 msec 13 p5-0.toucham.bbnplanet.net (4.24.117.66) 68 msec 68 msec 68 msec 14 den-edge-18.inet.qwest.net (205.171.16.34) 68 msec 68 msec 68 msec 15 208.46.255.14 120 msec 120 msec 120 msec 16 63.237.115.200 120 msec 120 msec 120 msec
ner-routes>sh ip bgp 205.171.16.34 BGP routing table entry for 205.171.16.32/30, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 0, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58 ner-routes>sh ip bgp 63.237.115.20 BGP routing table entry for 63.237.115.0/27, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 5, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58
Gotte filters?
On Mon, 22 Jan 2001, Jon Stanley wrote:
The part that I was particularly concerned about was where it left qwest for BBNPlanet and got right back on Qwest. I went ahead and gave them a call (at the number listed on Jared's page), and they asked for a traceroute, etc. I gave them all the research that I had done and they just kinda fell silent when they saw my email to them. Then they said "We'll have our NOC group take a look at this.". I thought that I had called the NOC!!!! Yet more examples of clueless morons manning the phones. (Not saying that my employer is not guilty of the same :-( ),
The guilty party is AS3908, but the truely sad part is the lack of filtering from their peers. Pass the pointy hat to bbn and c&w at a minimium. http://www.e-gerbil.net/ras/3908 by my count there are around 2500 routes, most of them /24 or longer (count the /30s). And when you try to email noc@sni.net... ... while talking to uswgne21.uswest.com.:
RCPT To:<luis.ayala@qwest.com> <<< 550 5.2.1 <luis.ayala@qwest.com>... Mailbox disabled for this recipient 550 luis.ayala@qwest.com... User unknown RCPT To:<daniel.dye@qwest.com> <<< 550 5.2.1 <daniel.dye@qwest.com>... Mailbox disabled for this recipient 550 daniel.dye@qwest.com... User unknown RCPT To:<erik.hanhy@qwest.com> <<< 550 5.2.1 <erik.hanhy@qwest.com>... Mailbox disabled for this recipient 550 erik.hanhy@qwest.com... User unknown RCPT To:<gregory.taylor@qwest.com> <<< 550 5.2.1 <gregory.taylor@qwest.com>... Mailbox disabled for this recipient 550 gregory.taylor@qwest.com ... User unknown ... while talking to [199.117.162.13]: RCPT To:<millerc@medusa.csn.net> <<< 550 <millerc@medusa.csn.net>... User unknown 550 millerc@medusa.csn.net... User unknown 550 troy@bobcat.sni.net... User unknown 550 <troy@bobcat.sni.net>... User unknown
-- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
On Mon, 22 Jan 2001, Richard A. Steenbergen wrote:
The guilty party is AS3908, but the truely sad part is the lack of filtering from their peers. Pass the pointy hat to bbn and c&w at a minimium.
http://www.e-gerbil.net/ras/3908 by my count there are around 2500 routes, most of them /24 or longer (count the /30s).
#sh ip bgp regexp _3908 <snip> Total number of prefixes 1059 It's sad when more than 1/2 of your announcements are caught by the filters. #sh ip prefix-list detail PEERS <snip> seq 10 deny 0.0.0.0/0 ge 25 (hit count: 8061, refcount: 4368661) <snip> --- John Fraizer EnterZone, Inc
On Mon, Jan 22, 2001, Jon Stanley wrote:
The part that I was particularly concerned about was where it left qwest for BBNPlanet and got right back on Qwest. I went ahead and gave them a call (at the number listed on Jared's page), and they asked for a traceroute, etc. I gave them all the research that I had done and they just kinda fell silent when they saw my email to them. Then they said "We'll have our NOC group take a look at this.". I thought that I had called the NOC!!!! Yet more examples of clueless morons manning the phones. (Not saying that my employer is not guilty of the same :-( ),
<off-topic> .. and since various companies keep hiring bright university students right off the bat, they don't get to spend time learning how the net works by working in a NOC. Which means, finding clueful people to staff a NOC is getting more difficult each day. Thanks guys. :-) </offtopic> Adrian -- Adrian Chadd "Sex Change: a simple job of outside <adrian@creative.net.au> to inside plumbing." - Some random movie
Each hop in a traceroute represents a -new- packet (actually 3) being sent out. Hence "Hopping back upstream" during BGP flap state. Remember "The Matrix" ? There is no spoon. ;) Jon Stanley wrote:
The part that I was particularly concerned about was where it left qwest for BBNPlanet and got right back on Qwest. I went ahead and gave them a call (at the number listed on Jared's page), and they asked for a traceroute, etc. I gave them all the research that I had done and they just kinda fell silent when they saw my email to them. Then they said "We'll have our NOC group take a look at this.". I thought that I had called the NOC!!!! Yet more examples of clueless morons manning the phones. (Not saying that my employer is not guilty of the same :-( ),
On Mon, 22 Jan 2001, Richard A. Steenbergen wrote:
On Mon, Jan 22, 2001 at 03:05:20AM -0500, Joe Budion wrote:
This one takes the cake for weirdest route I've ever seen:
10 p9-0.crtntx1-br1.bbnplanet.net (4.24.10.213) 48 msec 48 msec 44 msec 11 p15-0.crtntx1-br2.bbnplanet.net (4.24.10.114) 48 msec 48 msec 48 msec 12 p2-0.crtntx1-cr8.bbnplanet.net (4.24.8.198) 48 msec 48 msec 48 msec 13 p5-0.toucham.bbnplanet.net (4.24.117.66) 68 msec 68 msec 68 msec 14 den-edge-18.inet.qwest.net (205.171.16.34) 68 msec 68 msec 68 msec 15 208.46.255.14 120 msec 120 msec 120 msec 16 63.237.115.200 120 msec 120 msec 120 msec
ner-routes>sh ip bgp 205.171.16.34 BGP routing table entry for 205.171.16.32/30, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 0, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58 ner-routes>sh ip bgp 63.237.115.20 BGP routing table entry for 63.237.115.0/27, version 0 Paths: (1 available, no best path) 3908 4.24.117.66 (inaccessible) from 4.0.4.20 (4.24.0.207) Origin IGP, metric 5, localpref 100, valid, internal Community: 1:1001 209:209 209:30357 3908:900 Originator : 4.24.0.207, Cluster list: 4.0.4.20, 4.24.0.58
Gotte filters?
participants (5)
-
Adrian Chadd -
John Fraizer -
Jon Stanley -
Richard A. Steenbergen -
Richard Irving