[AusNOG] [Fwd: [bogon-announce] IANA IPv4 allocations and bogonupdate 1/8 and 27/8]

Mark Smith nanog at 85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org
Wed Jan 20 17:03:47 EST 2010


On Wed, 20 Jan 2010 12:54:33 +1000
"Steve Lisson" <SteveL at dedicatedservers.net.au> wrote:

> Unfortunately it is more common that what might think, there has been
> some discussion on Nanog regarding it (including comments like 'Most
> ISP's, if not all, null route 1.0.0.0/8 therefore you shouldn't
> encounter any problems using it in a private network.' and taking from
> Wikipedia:
> 
> http://en.wikipedia.org/wiki/Private_network
> 
> Private use of other reserved addresses
> 
> Several other address ranges, in addition to the official private
> ranges, are reserved for other or future uses, including 1.0.0.0/8 and
> 2.0.0.0/8[1]. Though discouraged, some enterprises have begun to use
> this address space internally for interconnecting private networks to
> eliminate the chance of address conflicts when using standards-based
> private ranges.[citation needed]
> 

Pigs can fly [citation needed]

http://en.wikipedia.org/wiki/File:Sus_scrofa_avionica.png

;-)

> Steve
> 
> -----Original Message-----
> From: ausnog-bounces at lists.ausnog.net
> [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Trent Lloyd
> Sent: Wednesday, 20 January 2010 12:42 PM
> To: surfer at mauigateway.com
> Cc: ausnog at lists.ausnog.net
> Subject: Re: [AusNOG] [Fwd: [bogon-announce] IANA IPv4 allocations and
> bogonupdate 1/8 and 27/8]
> 
> 
> On 20/01/2010, at 10:19 AM, Scott Weeks wrote:
> 
> > 
> > --- rdobbins at arbor.net wrote:
> > From: "Dobbins, Roland" <rdobbins at arbor.net>
> > 
> >> From what I heard one, 1.0.0.0/8 is a de facto standard for
> transitioning routers between large companies in the context of joining
> networks after a merger, or other forms of inter-company peering.
> > 
> > I've never hear of or run into this anywhere in the world, FWIW.
> Unallocated netblocks should never be used for such purposes due to the
> disruption caused when they're finally allocated, as is this case in
> this instance.
> > ---------------------------------------------
> > 
> > 
> > I inherited a network which we partitioned off from a big giant
> network who shall remain unnamed (starts with a V and ends with an N ;-)
> who used 113.52.0.0/16 for Hawaii on boxes that should not have to reach
> the outside world (but some do via NAT).  That was allocated to APNIC.
> Luckily the boxes don't need to reach the areas 113.52.0.0/16 was
> allocated to.  Yet.  So it definitely happens...
> 
> Yeah I had some random small business, which if I recall was a telstra
> managed router service.. anyway.. I don't recall which range but it was
> something like 100/8 was in use for the entire network.. and their other
> site (connected via VPN) used 101 or some other entire /8... complaint
> was "I can't get to site X".. wonder why ;)
> 
> Regards,
> Trent
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog



More information about the AusNOG mailing list