Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


What's with the 192.* block?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

What's with the 192.* block?

DStroutDStrout Member
edited February 2013 in General

It seems the IPs of many of the servers I get start with 192. DigitalOcean gives out IPs like that, my RamNode server has an IP from that block, I had a VPS for a short time from ShoveHost that had an IP from there, and my IPXCore DNS box does as well. The theory that I have (because I know next to nothing about networking. Routing? What's that?) is that since there is also a class of special local IPs (192.168.*) in the block, it's being handed out last as IPv4 depletion is coming down to the wire. But what do I know? Maybe it's just pure coincidence, but each time I get a new VPS like this, I get more curious, so can anyone tell me why this is?

«1

Comments

  • 192.0.0.0/24 wasn't meant to be handed out indeed, but this is what happens when you have a shortage and people willing to pay for more ;-)

  • Hello ipv4 shortage!

  • jkr1711jkr1711 Member
    edited February 2013

    Yeah I've noticed that too, recently got a 192.* IP with Dacentec

  • Arin have been using this to assign space the past few months.

    Only 192.168/16 is meant to be used for private space as per http://tools.ietf.org/html/rfc1918 so everything else is available.

  • @unused said: Only 192.168/16 is meant to be used for private space

    Also 192 was not meant to be given out, like, that's what they said to eachother (RIRs) before the shortage

  • RadiRadi Host Rep, Veteran

    I have:
    184.154.70.78
    94.249.203.121
    192.227.129.75 :D
    108.174.53.153
    108.174.53.154
    This are all my IP adresses.

  • @Radi said: 184.154.70.78

    94.249.203.121
    192.227.129.75 :D
    108.174.53.153
    108.174.53.154

    Brute force + ddos time

    /joke

  • Actually 192/8 was used for very long time, i see some assignments from 1992 there.

  • @rds100 said: i see some assignments from 1992 there.

    Oh, haha, too bad they still use ipv4 while ipv6 was designed in 1998 :-(

  • Arin's IP is in 192.0.0.0/8 ;)

  • @BronzeByte said: 192.0.0.0/24 wasn't meant to be handed out indeed...

    Well, as least I know enough about networking to make one correct educated guess. @all thanks for the answers.

  • @BronzeByte said: 192.0.0.0/24

    192.0.0.0/24 would only be 192.0.0.1-192.0.0.254. Maybe you meant 192.0.0.0/8 :P

  • DamianDamian Member
    edited February 2013

    If you're finding that 192.* is giving you an issue, we can change your IP to something else. We haven't really had any complaints about it, except that it doesn't have valid geolocation data, since it's a virgin block that was never issued before.

  • @KernelSanders said: Maybe you meant 192.0.0.0/8 :P

    Oops, I did, wasn't paying enough attention I guess

  • @Damian Not a problem, just something I've noticed that I was wondering about.

  • @BronzeByte said: Oops, I did, wasn't paying enough attention I guess

    Figured that hehe :P

  • Seems quite common lately, I've been assigned two blocks in the 192.110.xxx.xxx range which are new assignments too.

    Not had any complaints about it though.

  • We have a few 192. /20's for our company

  • RadiRadi Host Rep, Veteran

    I dream for a VPS with 8.8.8.* IP.

  • @Radi said: I dream for a VPS with 8.8.8.* IP.

    You don't want to know how much Google has paid for 8.8.8.8

  • Virtually every VPS I have is in 192/8 except for a few cases (prgmr.com is in 71/8, DO was handing out 185/8 for AMS, "host1free vps" in 94/8 and my initial CVPS (I know) was 96/8).

  • DStroutDStrout Member
    edited February 2013

    @Damian said: If you're finding that 192.* is giving you an issue, we can change your IP to something else.

    .

    @turbovm said: Not had any complaints about it though.

    To be clear, this isn't a complaint. I'm not having any trouble with my servers under this IP block, I just wanted to know why it was so prevalent.

  • Nick_ANick_A Member, Top Host, Host Rep

    @Damian said: If you're finding that 192.* is giving you an issue, we can change your IP to something else. We haven't really had any complaints about it, except that it doesn't have valid geolocation data, since it's a virgin block that was never issued before.

    I've had some people complain about home connections having trouble. Any my 192.73.x.x blocks seem to be geolocated in the UK :/

  • i have a few 192.* PI spaces, not unusual for very old assignments.
    Its one of the oldest RIPE used network (along with 193 and 194), ARIN owns the other half of it (after .168/16) and started allocating from it just a few months ago.

    So if you see 192/8 it's either a very old EU assignment or a new US assignment.

  • There's nothing wrong with 192 ip's, the private address block is 192.168.0.0/16 which is 192.168.0.0 to 192.168.255.255 65535 ip's.

    ARIN is handing out the other 192 blocks because that's what they are handing out at the time.

  • poor IPv4-all this hype today has me Paying close attention to IPv6 now-ahh yes IPv4, it was known as the Pavlova of the Protocols ..

  • @FRCorey said: ARIN is handing out the other 192 blocks because that's what they are handing out at the time.

    A short while back it was all 199.'s ;)

  • @sleddog said: A short while back it was all 199.'s ;)

    Yeah, I have one of those too.

  • MaouniqueMaounique Host Rep, Veteran

    You are lucky if you had no complaints, I was asked for a refund because i only gave "internal" IP.
    True, 192.165 is really-really close...

  • @Maounique said: True, 192.165 is really-really close...

    After years of typing 192.168 I find it really hard to type any other numbers after 192.... I find myself constantly backspacing

Sign In or Register to comment.