nanog mailing list archives
Re: Using private APNIC range in US
From: gordon b slater <gordslater () ieee org>
Date: Fri, 19 Mar 2010 06:08:56 +0000
On Thu, 2010-03-18 at 14:50 -0400, Daniel Senie wrote:
As you note, debugging this type of thing is often not intuitive, as everything appears to work from almost everywhere
I got curious yesterday and set off a couple (very slow {option -T0}, very polite, very restrictive) nmap single port scans of a few lumps of 1.0.0.0/22 yesterday, but couldn't see much out there due to my several of our ISPs internal boxes. It looks like chaos-squared out there. I don't envy anyone fathoming that stuff out for real. Still, that said, the transition to fully signed roots seems to be going along without too much breakage (I think/hope!) so maybe only time will tell how much this latest block release will give trouble longterm. Gord -- rockin ze chair mit Davey Graham to Banshee from rackserver-2
Current thread:
- Re: Using private APNIC range in US, (continued)
- Re: Using private APNIC range in US Jared Mauch (Mar 18)
- Re: Using private APNIC range in US William Allen Simpson (Mar 18)
- Re: Using private APNIC range in US Larry Sheldon (Mar 18)
- Re: Using private APNIC range in US Matt Shadbolt (Mar 18)
- Re: Using private APNIC range in US Charles Mills (Mar 19)
- Re: Using private APNIC range in US Craig Vuljanic (Mar 19)
- RE: Using private APNIC range in US Eric J Esslinger (Mar 19)
- Re: Using private APNIC range in US Graham Beneke (Mar 20)
- Re: Using private APNIC range in US Ćukasz Bromirski (Mar 20)
- Re: Using private APNIC range in US Daniel Senie (Mar 18)
- Re: Using private APNIC range in US gordon b slater (Mar 18)
- Re: Using private APNIC range in US gordon b slater (Mar 18)