RE: [afnog] ARIN to allocate from 74/8 & 75/8
I put up some pre-run queries for these prefixes based on the routeviews data at: http://bgpinspect.merit.edu/reports.php But you can probably run these yourself if you like.
From the perspective of atleast the 5 routeviews peers we track(att, level3,aol,sprint,glx), all prefixes are pretty much visible by now, what is perhaps more interesting is that it looks like these(and a bunch more) were being incorrectly announced by AS9802 prior to Aug 30th.
-manish
Date: Wed, 21 Sep 2005 08:38:11 -0400 From: "Hannigan, Martin" <hannigan@verisign.com> Subject: RE: [afnog] ARIN to allocate from 74/8 & 75/8
if it's useful, i'd be happy to report what percentage of my peers have/don't have routes to these prefixes.
I'd be interested.=20
Best, ---------------------
thanks for the routing visibility update. due to filtering issues at the hosting provider of the cymru pingable, the data plane story is not as sanguine. i am told it will not be fixed until the weekend. this means that, if you are having problems pinging the target, wait until next week to spend time tearing your hair out debugging your configs. randy
Hi, NANOGers. ] due to filtering issues at the hosting provider of the cymru ] pingable, the data plane story is not as sanguine. i am told ] it will not be fixed until the weekend. That's not quite correct. :) One of our transit providers had some outdated filters, and these have now been updated. This was not the case with our other transit providers. Depending on the path you took to reach our test network, you may or may not have seen a problem. Note that we are already seeing cases were a network will accept and propagate the prefixes, yet have ACLs or other filters in place that block access to them. In other words, check both your BGP views and a ping or traceroute. We're working with two large providers now, and hope to have their filters updated shortly. As we come across problems, we are reaching out to folks and asking them to make the necessary updates or fixes. YOUR input helps us to locate those trouble spots and get them corrected before this address space is allocated to production networks. You can also help by referencing the latest Bogon list. <http://www.cymru.com/Bogons/index.html> Or make it easy on yourself and let Team Cymru do all the work. Fire up a peering session to the Bogon route-servers today! <http://www.cymru.com/BGP/bogon-rs.html> As always, if you are having difficulty reaching the three test IP addresses, please drop us a note at team-cymru@cymru.com. Thanks! Rob. -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999.
On Thu, 22 Sep 2005, Manish Karir wrote: Thanks! I don't understand something. Quoting from your page: "Based on the above data, we can see that both these prefixes were being (probably incorrectly) announced by AS9802 (CHINA-21VIANET 21vianet(China) Inc.) prior to Aug 30, at which time they withdrawn and re-announced by AS36666 (Team Cymru testing?)." The ASpath was: 7018 6461 4134 4847 9308 9802 or 3356 3561 4134 4847 9308 9802 or 1239 6461 4134 4847 9308 9802 Ignoring the Chinese ASNs, AS3561 (Savvis) or AS6461 (Abovenet) should have been checking AS4314 and all their downstream announcements for IP hijacking. Is this not being done? -Hank
I put up some pre-run queries for these prefixes based on the routeviews data at: http://bgpinspect.merit.edu/reports.php
But you can probably run these yourself if you like.
From the perspective of atleast the 5 routeviews peers we track(att, level3,aol,sprint,glx), all prefixes are pretty much visible by now, what is perhaps more interesting is that it looks like these(and a bunch more) were being incorrectly announced by AS9802 prior to Aug 30th.
-manish
participants (4)
-
Hank Nussbacher -
Manish Karir -
Randy Bush -
Rob Thomas