Slashdot Mirror
Free IPv4 Pool Now Down To Seven /8s
Zocalo writes "For those of you keeping score, ICANN just allocated another four /8 IPv4 blocks; 23/8 and 100/8 to ARIN, 5/8 and 37/8 to RIPE, leaving just seven /8s unassigned. In effect however, this means that there are now just two /8s available before the entire pool will be assigned due to an arrangement whereby the five Regional Internet Registries would each automatically receive one of the final five /8s once that threshold was met. The IPv4 Address Report counter at Potaroo.net is pending an update and still saying 96 days, but it's now starting to look doubtful that we're going to even make it to January."
And the best part for ISPs is, NAT turns the Internet from its inherent peer-to-peer nature into a client/server architecture where all home users can be relegated to "content consumers" under cover of IP4 address shortages. Score!
I'm frankly terrified that the "solution" to this is not to fix the underlying issue, but instead to layer work-arounds on it.
Not to mention, unless I'm much mistaken a NAT can support 65536 connections at maximum (number of valid ports for outgoing connections). A /8 network might be okay, but putting a larger network behind NAT isn't going to help, and you can't layer them (because you still need a port free for the connection). We're going to run out, NAT just delays the inevitable by layering a giant administrative headache on the top.
Lets say your ISP assigns you 10.0.32.128. Now, kindly tell me how you plan to connect to your home PC from work.
What will make it even more fun is if you have two branch offices of the same company connected to the different ISPs getting 172.16.32.66 and 10.0.65.88, how do you set up a VPN between them?
I am a lawyer and this constitutes legal advice and I shall indemnify you against any losses arising from taking it.