North America Runs Out of IPv4 Addresses
DW100 writes: The American Registry for Internet Numbers (ARIN) has been forced to reject a request for more IPv4 addresses for the first time as its stock of remaining address reaches exhaustion. The lack of IPv4 addresses has led to renewed calls for the take-up of IPv6 addresses in order to start embracing the next era of the internet.
The sky is falling!
The sky is falling!
It hit me on the head! *OW! NOT THAT ONE!*
"Runs out".
Yeah. Okay. And how many companies are sitting on vast blocks that are only partially tapped?
This isn't so much an issue of lack (though at some point it'll become that).
It's an issue created by how assignment of address blocks was and is managed.
Chas - The one, the only.
THANK GOD!!!
Everyone I know just uses 127.0.0.1. What do we need all these new ones for?
I'm only using 8 addresses out of my 192.168.1.1/24 class C block, I could probably be talked into auctioning off the other 240+ addresses. Call me, maybe?
these companies (which I'd love to name) missed the boat when IPv4 address costs (for sale) was highest and are actually waiting for this next "crisis" in hopes that they can get billions for Class A nets (these companies date back to "the beginning" and the use their Class A addresses for non-Internet facing internal addressing (that is they are wasting the addresses) simply because they lack the skills to change).
IBM has the technical know-how to stop using routable addresses internally, but their class A is part of their culture. I imagine the same is true for other class A holders.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Meh.
Whatever.
Never answer an anonymous letter. - Yogi Berra
My cell phone has been on IPv6 for years. Everything I have is ready for the conversion. What is holding it up?
There is a small interesting detail about IPv6 that is almost never mentioned. An IPv6 address counts 128 bits. Typically the "top" 64 bits are provided by your ISP and will be used to route the packets through the Internet. The 64 remaining LSb have to be unique within the subnet (typically a LAN), and usually these 64 bits are made from the MAC address of the interface linked to this IPv6 address (padded if 48 bits). That means for instance that knowing your IPv6 address, someone is likely to know also your MAC address (of the device used), that is usually the maker/configurator of the NIC (eg Apple, MS ...). And if the shop where you bought the device keep track of your MAC address - like Apple for instance - they may be able to identify you precisely, based on your IPv6 address (eg when you access their web site).
Slashdot, fix the reply notifications... You won't get away with it...
It's correct to use assigned addresses for internal hosts. The point is they're unique — you can set up a tunnel between any two organisations, or merge two networks, and not have to renumber things because both were using 10/8.
The cost to renumber and use their assignment more efficiently would be huge, similar to the cost to move to IPv6 but with little gain.
Get off my internet!
All the routers i've seen implement statefull filtering on ipv6 and allow all outbound and no inbound (except traffic related to an outbound connection) by default, which is functionally identical to their ipv4 nat implementation.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
Every couple of weeks or so, I turn off V4 to see what happens. /. is one of the sites that I can't reach when I do.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
It wasn't crying wolf, at that time the growth was amazing and the policies for handing out IPs were much looser. They also didn't factor in for the facts that the policies would be changed and people would NAT NAT as Xzibit hadn't yet taught us about doing things while we're doing things. If NAT hadn't become so common we would have run out of IP addresses a very long time ago.
If they hadn't "cried wolf" then, I can only imagine how long ago we would have hit this point as we wouldn't have made adjustments to practices to push it into the future.
It's amazing how many morons will see that the rate at which a massive problem is coming is slower than anticipated and conclude that it's not a real problem. It's usually better to err on the side of caution and expedience as you rarely do things to quickly with regards to large problems.
If you think "routable" and "insecure" are synonyms, you're going to have a hell of a time with IPv6