4 ms·

That's funny. I use 1.0.0.0/24 for my home network. Perhaps they're doing something similar.

lathiat 9y ago
You are part of the reason we have these problems :( While that's probably never getting allocated at this point, that's also what everyone thought 10-20+ years ago about 1.0.0.0/8 and yet here we are. When my organisation was allocated from 110.0.0.0/8 a few years back we were constantly seeking out others to remove us from their "bogon" filters blocking unallocated ranges that were static and not being maintained. Including big organisations like Commonwealth Bank of Australia. It was a real pain. Meanwhile the security advantage of this behaviour is highly dubious in my view - just as easy to steal an otherwise valid but un-used (or even used) prefix. Thanks for reading my rant this far if you did, I'll return you to your regularly scheduled more insightful comments....... now.
- jason_slack 9y ago
  I worked for a company once where each department had a public IP space, like 97.0.0.x or 98.0.0.x. When I told the network guy this wasn't proper and we should be using 192.168.x.x or 10.x.x.x he laughed and said "it really doesn't matter, nobody cares". To make all of these networks talk, share, etc they had to use a punch of equipment to tie each one in and then out via a Time Warner Road Runner circuit. This was about 1999 :-)
  - Spivak 9y ago
    It seems as though the conventional wisdom has changed, because in my large org every device is assigned a public IP and access is controlled by our border firewall. It's weird how much NAT has changed the thinking about network organization -- if you have the addresses you should get into the IPv6 state of mind -- publicly address all the things! Now if your org picked 97/98 arbitrarily without actually owning the addresses relying on the fact that you wouldn't actually get routed any public traffic then that's a different story.
    - corymacd 9y ago
      I too have worked at organizations that have been configured like this. I speculate that pressure on the limited IPv4 allocations has caused many places that had previously been configured with large public IP blocks, to sell sub-allocations, for profit. NAT certainly does enable this practice but isn't the root cause. Sell those IPv4 blocks for $$$ -- who needs their laptop getting a public IPv4 address anyway?
theandrewbailey 9y ago
Be legit and use 10.0.0.0/24, or even 10.0.0.0/8 instead.
- duskwuff 9y ago
  Or a subnet of 172.16.0.0/12 if you want to be a hipster. :) (Or if you need to interact with other networks that use the other RFC1918 subnets -- hardly anyone uses 172.16.)
  - F_r_k 9y ago
    I deal with lots of devices we put on customers networks. The problem is that 172.16.0.0/12, 10.0.0.0/8 and 192.168.0.0/16 are all used by customer networks. It's a pain when setting up VPN addressing. Thus I chose 11.0.0.0/16 (sadly not possible to use IPv6). My devices will never need to reach DoD, so that's very convenient.

You are part of the reason we have these problems :( While that's probably never getting allocated at this point, that's also what everyone thought 10-20+ years ago about 1.0.0.0/8 and yet here we are. When my organisation was allocated from 110.0.0.0/8 a few years back we were constantly seeking out others to remove us from their "bogon" filters blocking unallocated ranges that were static and not being maintained. Including big organisations like Commonwealth Bank of Australia. It was a real pain. Meanwhile the security advantage of this behaviour is highly dubious in my view - just as easy to steal an otherwise valid but un-used (or even used) prefix. Thanks for reading my rant this far if you did, I'll return you to your regularly scheduled more insightful comments....... now.

jason_slack 9y ago
I worked for a company once where each department had a public IP space, like 97.0.0.x or 98.0.0.x. When I told the network guy this wasn't proper and we should be using 192.168.x.x or 10.x.x.x he laughed and said "it really doesn't matter, nobody cares". To make all of these networks talk, share, etc they had to use a punch of equipment to tie each one in and then out via a Time Warner Road Runner circuit. This was about 1999 :-)
- Spivak 9y ago
  It seems as though the conventional wisdom has changed, because in my large org every device is assigned a public IP and access is controlled by our border firewall. It's weird how much NAT has changed the thinking about network organization -- if you have the addresses you should get into the IPv6 state of mind -- publicly address all the things! Now if your org picked 97/98 arbitrarily without actually owning the addresses relying on the fact that you wouldn't actually get routed any public traffic then that's a different story.
  - corymacd 9y ago
    I too have worked at organizations that have been configured like this. I speculate that pressure on the limited IPv4 allocations has caused many places that had previously been configured with large public IP blocks, to sell sub-allocations, for profit. NAT certainly does enable this practice but isn't the root cause. Sell those IPv4 blocks for $$$ -- who needs their laptop getting a public IPv4 address anyway?

theandrewbailey 9y ago

Be legit and use 10.0.0.0/24, or even 10.0.0.0/8 instead.

duskwuff 9y ago
Or a subnet of 172.16.0.0/12 if you want to be a hipster. :) (Or if you need to interact with other networks that use the other RFC1918 subnets -- hardly anyone uses 172.16.)
- F_r_k 9y ago
  I deal with lots of devices we put on customers networks. The problem is that 172.16.0.0/12, 10.0.0.0/8 and 192.168.0.0/16 are all used by customer networks. It's a pain when setting up VPN addressing. Thus I chose 11.0.0.0/16 (sadly not possible to use IPv6). My devices will never need to reach DoD, so that's very convenient.