What's special about 151&152.0.0.0 Blocks

msv · ‎02-23-2010

I saw a config recently with the above ranges. I assumed it was valid external IP's, but it seems these blocks are not routable on the Internet.

What is so special about these blocks?

Thanks

paolo bevilacqua · ‎02-23-2010

What search results can you bring to support your point ?

inetnum:         151.0.0.0 - 151.255.255.255
netname:         EU-ZZ-151
descr:           Various Registries
country:         EU # Country is really world wide
remarks:         These addresses were issued by
              The IANA before the formation of
              Regional Internet Registries.
              <>
org:             ORG-NCC1-RIPE
admin-c:         IANA1-RIPE
tech-c:          IANA1-RIPE
status:          ALLOCATED UNSPECIFIED
mnt-by:          RIPE-NCC-HM-MNT
mnt-lower:       RIPE-NCC-HM-MNT
mnt-routes:      RIPE-NCC-RPSL-MNT
source:          RIPE # Filtered

msv · ‎02-23-2010

If you lookup these blocks on ARIN, etc. they are not assigned to anyone. Ran traceroute from a few of my internet routers, and it didn't go anywhere, and no bgp routes for it

paolo bevilacqua · ‎02-23-2010

ARIN dbase can have gaps. As you see, these are European numbers. For some reason 151.x.x.x is also familiar to me.

Giuseppe Larosa · ‎02-23-2010

Hello Paolo,

>> For some reason 151.x.x.x is also familiar to me.

Telecom Italia AS3269 uses some of 151.x.x.x

MSV:

yes, 151.0.0.0 and 152.0.0.0 are not present in public internet table, this means they are not assigned but does not imply they are not public routable addresses.

Hope to help

Giuseppe

vmiller · ‎02-23-2010

my quick look showed no 151.0 or 152.0 netblock. they

are class b, starting at 15x.1

152.1.x.x is NC state Univeristy

151.1.x thru 151.100 is:

OrgName:    RIPE Network Coordination Centre
OrgID:      RIPE
Address:    P.O. Box 10096
City:       Amsterdam
StateProv:
PostalCode: 1001EB
Country:    NL

CIDR:       151.1.0.0/16, 151.2.0.0/15, 151.4.0.0/14, 151.8.0.0/13, 151.16.0.0/12, 151.32.0.0/11, 151.64.0.0/11, 151.96.0.0/14, 151.100.0.0/16
NetName:    RIPE-ERX-151-1-0-0
NetHandle: NET-151-1-0-0-1
Parent:     NET-151-0-0-0-0
NetType:    Early Registrations, Transferred to RIPE NCC
Comment:    These addresses have been further assigned to users in
Comment:    the RIPE NCC region. Contact information can be found in
Comment:    the RIPE database at http://www.ripe.net/whois
RegDate:    2003-04-02
Updated:    2003-06-18

msv · ‎02-23-2010

to be exact, they were using 151.0.0.0/24 & 152.0.0.0/24

Brandon Svec · ‎02-23-2010

Interesting thread. Just to add- I recently came across a customer using 128.66.0.0/16 internally and I was sure it was not correct. They argued otherwise and I found this interesting link while researching:

http://lists.arin.net/pipermail/arin-discuss/2009-September/001500.html

I still think it is incorrect and you should always use rfc1918 for internal, but they may have had some point at least..

brandon

-- please remember to rate and mark answered helpful posts --

paolo bevilacqua · ‎02-24-2010

Hi Brandon how are ya m8 ?

What happens, sometime people is not happy with the standard private space, mainly because everyone else is using it. They are afraid that it will overlap with other part of the network, a company acquisiton, or it just looks more serious. I also have seen ISPs that literally ran out of private space. So at that point they begin guessing which public space has the less chances to be ever used on the Internet. From there some wild picks, 23/8, 128, 151 and whatelse.

Riight or wrong, that is what is being done everyday.