Something wrong with this?
sho ip bgp 137.39.0.0 255.255.0.0 BGP routing table entry for 137.39.0.0/16, version 533944 Paths: (2 available, best #2, advertised over IBGP) 174 192.41.177.245 from 192.41.177.245 Origin IGP, metric 30, localpref 100, valid, external Community: 2548:668 701 198.32.186.248 from 198.32.186.248 (137.39.3.57) Origin IGP, metric 2, localpref 100, valid, external, best Community: 2548:668
*174*? -- jamie g.k. rishaw dal/efnet:gavroche IAGnet/CICNet/netILLINOIS 'whois JGR2' for PGP keyID/Fingerprint __ Network Operations/TSD DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 "The machine's fine. It just doesn't work." -dan@nic.net
Something wrong with this?
sho ip bgp 137.39.0.0 255.255.0.0 BGP routing table entry for 137.39.0.0/16, version 533944 Paths: (2 available, best #2, advertised over IBGP) 174 192.41.177.245 from 192.41.177.245 Origin IGP, metric 30, localpref 100, valid, external Community: 2548:668 701 198.32.186.248 from 198.32.186.248 (137.39.3.57) Origin IGP, metric 2, localpref 100, valid, external, best Community: 2548:668
*174*?
What's really criminal is that neither of them have NOCs. randy
Something wrong with this?
sho ip bgp 137.39.0.0 255.255.0.0 BGP routing table entry for 137.39.0.0/16, version 533944 Paths: (2 available, best #2, advertised over IBGP) 174 192.41.177.245 from 192.41.177.245 Origin IGP, metric 30, localpref 100, valid, external Community: 2548:668 701 198.32.186.248 from 198.32.186.248 (137.39.3.57) Origin IGP, metric 2, localpref 100, valid, external, best Community: 2548:668
*174*?
What's really criminal is that neither of them have NOCs.
From private mail I received, it is clear that I was being too subtle.
UUNET and PSI have perfectly fine NOCs. The problem was that Jamie seems not to know how to use them and posts to nanog in stead. Folk, it is no longer safe to assume that clueful folk from provider X read this list. They have been driven off by the noise. Some weeks back, folk on a private list asked for anyone who still read nanog to copy over any useful message. None have been copied. This one certainly won't be. :-) randy PS: This is an actual bug. I do not think PSI has bought UUNET.
Oh, I'm sorry. This was a technical issue. You know. One national provider advertising the /16 of another national provider's *backbone*. Sorry. I'll refrain from such things like this in the future. I forgot. Today was an odd-numbered day. Can't talk tech on nanog. Shame on me. :-P
Something wrong with this?
sho ip bgp 137.39.0.0 255.255.0.0 BGP routing table entry for 137.39.0.0/16, version 533944 Paths: (2 available, best #2, advertised over IBGP) 174 192.41.177.245 from 192.41.177.245 Origin IGP, metric 30, localpref 100, valid, external Community: 2548:668 701 198.32.186.248 from 198.32.186.248 (137.39.3.57) Origin IGP, metric 2, localpref 100, valid, external, best Community: 2548:668
*174*?
What's really criminal is that neither of them have NOCs.
From private mail I received, it is clear that I was being too subtle.
UUNET and PSI have perfectly fine NOCs. The problem was that Jamie seems not to know how to use them and posts to nanog in stead.
Folk, it is no longer safe to assume that clueful folk from provider X read this list. They have been driven off by the noise. Some weeks back, folk on a private list asked for anyone who still read nanog to copy over any useful message. None have been copied. This one certainly won't be. :-)
randy
PS: This is an actual bug. I do not think PSI has bought UUNET.
-- jamie g.k. rishaw dal/efnet:gavroche IAGnet/CICNet/netILLINOIS 'whois JGR2' for PGP keyID/Fingerprint __ Network Operations/TSD DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 "The machine's fine. It just doesn't work." -dan@nic.net
jamie g.k. rishaw wrote:
Something wrong with this?
sho ip bgp 137.39.0.0 255.255.0.0 BGP routing table entry for 137.39.0.0/16, version 533944 Paths: (2 available, best #2, advertised over IBGP) 174 192.41.177.245 from 192.41.177.245 Origin IGP, metric 30, localpref 100, valid, external Community: 2548:668 701 198.32.186.248 from 198.32.186.248 (137.39.3.57) Origin IGP, metric 2, localpref 100, valid, external, best Community: 2548:668
*174*?
Hmm. That route looks ok to us where we learn it from PSI in New York: 100 BGP 137.39/16 195.11.50.2 (2529) 174 701 IGP However, something is certainly odd somewhere: GateD-beech.router.demon.net> show ip routes 100 IP radix tree: 94528 nodes, 49200 routes GateD-beech.router.demon.net> We have a few thousand more routes than normal, including this more specific route that includes 'www.uu.net' that we see via EBONE->ICM->Sprint but not via PSI or MCI. GateD-beech.router.demon.net> show ip walkup 199.170.0.30 100 BGP 199.170/24 194.159.252.88 (2529) 5417 1755 1800 1239 701 IGP 100 BGP 199.170/15 195.11.50.2 (2529) 174 701 IGP Anyone else seeing weirdness ? Regards, Andrew -- Andrew Bangs, Network Engineering Team Leader, Demon Internet Ltd andrewb@demon.net http://www.demon.net/ http://www.demon.nl/
participants (3)
-
Andrew Bangs -
jamie＠intuition.iagnet.net -
Randy Bush