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."
Last IP!!
I Have 2 that I'm not using anymore, perhaps I should put them on ebay? ;-)
ipv6 is my vpn
So, I keep hearing all this news about them running low... What happens when we run out?
-Taylor
Worldwide Military budgets: $2100 billion. Worldwide Space Exploration budgets: $38 billion. Really, world? Really?
How will I ever be able to use my twittering armchair fart detector?
... since the unexpected end of the century in '99.
(What is actually surprising is that the internet still hasn't widely adopted IP6, and ISPs are now turning to ludicrous measures - NAT - to keep avoiding what makes sense.)
IPV6 anybody? (new meme anybody?)
Do not mock my vision of impractical footwear
where is ATT and comcast with IPV6?
Class E? That "reserved" block, for "future expansion"? That "future expansion" would be now.
There you go, another 16 blocks to break out. Plus the 7 we already have, that makes 385,875,968 addresses left still unallocated. Still over a third of a billion to go, which should be more than enough time for everyone to replace equipment that doesn't support IPv6, and deal with applications like Teredo that leak IPv6 address space across NATs and through VPNs.
end of line
Another non-functioning site was "uncertainty.microsoft.com."
The purpose of that site was not known.
NAT Time!
Granted, it is not a solution for everything, but there are just TONS of networks that could be behind NAT's and don't need anywhere near the IPV4 space they have. I have a feeling NATing will suddenly become a lot more popular.
Are there any cool exploits which will emerge between the used up pool and IPV6 adoption? Will collisions happen?
Let it burn to the ground and start fresh. IPv256! Decentralized DNS! All the good stuff. Oh well.
I can handle blocking IPv4 blocks based on geography given I have a US oriented website. But if you guys think you're going to unleash spammers from hell on me with a gazillion IP addresses, think again. As far as I'm concerned, you can give IPv6 to the Russians and Chinese on their own spam network.
The range of IPv4 addresses these people spam from is insane. Just give them back to us and go take IPv6 and spam yourselves into oblivion.
rd
Remember before Y2k almost all computer manufacturers placed "Y2k Compliant" or "Y2k Ready" logos on everything from bare computer cases to speakers? Well I cant wait for my "IPv6 Ready" USB keyboard...
Take em back! If we run out just reassign them. Do we really need an internet connected refrigerator to tell us that we need milk and $grocer has the best price?
Would someone tell me how this happened? We were the fucking vanguard of addressing in this country. The ICANN IPv4 class/8 was the block to own. Then the other guy came out with a IPV6 block. Were we scared? Hell, no. Because we hit back with a little thing called NAT. That's network address translation. For flexibility. But you know what happened next? Shut up, I'm telling you what happened--the bastards went to IPV6 tunnels. Now we're standing around with our cocks in our hands, selling four octets and a NAT. Flexibility or no, suddenly we're the chumps. Well, fuck it. We're going to five octets.
Sure, we could go to IPV6 next, like the competition. That seems like the logical thing to do. After all, IPV4 worked out pretty well, and IPV6 is the next number after IPV5 which seems to have disappeared. So let's play it safe. Let's make a longer address and call it the 4aff:fe0e. Why innovate when we can follow? Oh, I know why: Because we're a business, that's why!
Does anybody wanna buy an......eight? http://www.youtube.com/watch?v=rfelvI_ikf4
Whens slashdot going to go ipv6?
(see subject)
IPv4 is dying - Netcraft confirms it, bla bla...
In the mean while, why not simply create some IP addresses? As long as you keep them to yourself, no-one will complain...
Because I'm on it right now yet I see no AAAA record. Pretty much anyone on Comcast can get a 6rd address at the drop of a hat; native dual stack is coming. Other providers will have to get on the bandwagon soon I gather. Whine endless about the end of ipv4 after you've already made arrangements to join the modern age.
For years now I have had this netbsd box as my front end. The DSL modem plugs into an ethernet port on the PC which NATs in two directions: a local hard wired network and wifi. So after y'all slashdotted by server I stated looking at a rebuild around this nice fast AMD64 machine but it is light on PCI slots so I can't have the two ethernet cards plus atheros wifi plus serial that I need.
So last night I splashed out on a Netcomm wifi router and the plan I formulated later in the evening was to use it as my front end with the DMZ trick pointing to the BSD box.
Then this morning the penny dropped. NetBSD supports IPv6 perfectly well but the netcomm configuration pages don't mention it. But most people use these little wifi routers. Are they screwed? Am I screwed if I rely on this router?
http://michaelsmith.id.au
what needs "public" IPs? What /really/ needs them? routing interfaces between networks, and websites using ssl. Since a very large percentage of the web surfing population is still using windowsXP or older, we can't use TLS (which has been around for ages). So instead, every single ssl-enabled site needs it's own IP. I work at a small company, and even we could release hundreds of public IPs if WindowsXP could use tls instead of ssl.
Will everyone using Hamachi be unable to reach whoever gets a 5/8 address?
It is IANA--Internet Assigned Numbers Authority--not ICANN that allocates IP addresses. They also do things like port and protocol numbers.
But can someone explain to me why IPv6 didn't just extend the IPv4 format logically and stylistically? Why not just tack on more numbers? And all existing numbers could be assumed
For instance,
209.85.225.147
becomes
1.1.209.85.225.147
Instead, we break convention to use colons and hex, ie. 3ffe:1900:4545:3:200:f8ff:fe21:67cf
It seems to me adoption could have been a lot quicker and less painless.
If you examine the currently alloted /8 addresses it seems really silly to say they are exhausted.
I would rather say the current assignment is being poorly used at the moment.
http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks
This is about 1/5th of our total pool being thrown around rather carelessly. It would probably on buy a few more years to reclaim these addresses and chop them up, but surely the problem is just poor usage as opposed to exhaustion.
Not that I think any type of recycling or waste management will actually happen in the IP space, but I do like complaining about it.
"You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
How long before I can get the address 255.255.255.255? I wanna set up a website called 'endoftheinternet.com'!
"I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)
Can we PLEASE make a concerted effort towards ipv6 now please? Microsoft are even encouraging use of it via DirectAccess ("vpn less" ipv6 secure tunnel), and god knows they're nowhere near leading edge as far as standards support goes.
I fear that ISPs are just going to do retarded shit like NATing their entire customer base though, but it really is just delaying the inevitable and causing breakage anyway...
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
I thought there were 9 pieces of 8 available and if you had one you'd be one of the pirate lords.
I don't know, but I sure hope someone starts working on a solution soon! It sounds like solving this problem might take a while!
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
008/8, does Level3 need two /8s? /8s? /8s?
016/8, does HP(?) need two
026/8, 029/8, 030/8, does DISA need 4
Do all of these guys need a /8? Can they be required to hand back a /9?
034/8 Halliburton
035/8 MERIT Computer Network
038/8 PSINet
040/8 Eli Lily
048/8 Prudential Securities
052/8 E.I. duPont de Nemours
053/8 Cap Debis CCS
054/8 Merck
www.ipv4depletion.com seems to have had a more accurate prediction than the Potaroo site for quite some time.
ipv6 ready!
Well, that was fun while it lasted. Time to shut down the Internet.
Why is IPv6 not based on MAC adresses? I've never understood this. Every piece of electronics capable of connecting to a network has at least one unique hardware id already. Why do we need a new one? Is there are reason not to just use this number? Or have I misunderstood, and this actually IS the plan.
Damn! I wanted 37/8!
http://alternatives.rzero.com/
This might have been a good case for accepting the proposal 'Redesignation of 240/4 from "Future Use" to "Private Use"': ... as beneficiaries would have some degree of control over the equipment linking the two sites. However the proposal is expired.
http://tools.ietf.org/html/draft-wilson-class-e-02
1. There are enough IPv4 addresses available in US to cover pretty much everyone. So no issue here. Since I live in US, frankly, that's all the answer I need.
2. If there aren't enough IPv4 addresses - take away anything allocated to China, they don't use Internet in a fair or reasonable way anyway. Let them live in their own private little world.
3. NAT - because I only need 1 (one) IP address for my entire household. I decidedly don't want any of my multiple devices to be separately and individually addressable. (By the same token my fridge does not have a separate mailing address or a phone number, you have to call or write to *me* before you get to talk to it - if that's your thing of course)
4. Trading IP addresses and packing. It's a resource - and it will be dealt with as such.
5. If only people that designed IPv6 "by committee" though a bit about real world and technology, IPv6 would have been much easier to implement. 128 bit addresses are a *wrong* size. They should have set the size at 64 bit. 64 bit values are now natively manipulated by much of computer hardware, so just as the new protocol would come into wider use, it would be conveniently supported by many algorithms relying on hardware. Now go build a radix tree for a routing table of 128 bit IPv6 addresses - let's see how well that works.
6. IPv6 in default implementation wants to use your MAC address as part of the IP. I don't know, perhaps a few of those big companies that like tracking people so much may be interested in that. I am not.
In conclusion - I'll wait till stuff begins crashing around. May be then someone will come up with a better solution than a deadborn poorly designed IPv6 we have now.
One particular issue is web host control panels - of the major control panels (cPanel, DirectAdmin and Plesk), only DirectAdmin has IPv6 already, and many web hosts aren't willing to deploy a different control panel just to get to IPv6. Hence many websites simply can't go IPv6 easily until the ISP upgrades to the control panel, and in the case of cPanel, which is by far the most popular one, there is not even a roadmap date for v6. Same goes for Plesk apparently.
If you use cPanel, see http://forums.cpanel.net/f145/case-10334-make-cpanel-ipv6-compatible-35453.html and comment if you want to see IPv6.
If you use Plesk, see http://forum.parallels.com/showthread.php?t=102770
What about now Hamachi and big ISPs (like Fastweb, in Italy) who happily use 5/8 ip addresses?
-->keep the frequency clear
IPv5 was the experimental ST2 protocol ( http://www.faqs.org/rfcs/rfc1819.html ). It was sort of a connection oriented IP designed for multimedia stuff. Nobody seemed to want that either. RSVP was a protocol designed to reserve bandwidth on the Internet, but ran on good old IPv4. That tanked as well.
The European Telecom research agency, ETSI, is working on yet another attempt to provide resource reservation through the Internet for VOIP. We'll see how that one goes.
Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
There's still plenty of space available if the various registries were proactive and found out what space was no longer used, never used, or used in networks which don't directly connect to the Internet (i.e. US military). I have more IP space than I can ever use ( class B and a bunch of class Cs) so I'd profit greatly if this space become a fungible commodity. But really, this is a solvable problem.
Yes, I've got it and it's completely legit. I am not going to reveal the IP space here because it will end up being attacked by jealous nerds. Yea $1/IP/mo, and you ISPs know you can charge twice that to your customers and they'll pay, because they have to. Around 66,500 addresses available, in a variety of sizes.
Oh, yes, I should add, this is not a joke.
It seems to me adoption could have been a lot quicker and less painless.
Whether we write down numbers in base 16 or base 256 (each digit in base 10) doesn't make one iota of difference to the upgrade difficulties.
The real problem, one of them at least, as far as I understand, is the lack of incentive for individual people and organizations to move towards IPv6: it's all cost no gain, because none of the parties you want to talk to are on IPv6, and the IPv4 address space isn't embedded in the IPv6 space.
Upgrade IP stacks that don't support it (Windows, IOS I think, etc) and start using the "reserved" Class E:
240.0.0.0-255.255.255.255 (268435456 adresses)
There you go with 268 million more addresses, worth at least another couple of years of more, if not bound to limiting RIR redistribution bureaucracy as it is now.
It the use of Class E a heavy and costly operation that a win of 2 years time would not justify? I don't think so.
It's also responsibility of the nakers of TCP/IP stacks that decided to ignore that completely: it was defined as "Reserved", not "Invalid".
All this panic for the end of IPv4 is not justified, like no panic was justified for the W2K bug.
1) It could lead to a black market of IPs
2) It will make the situation around RIRs unnecessarily tense
3) It might endanger net neutrality
There world will not go black at the end (at the real end, not at the bureaucratic end) of IPv4.
The market will suffer a bit from the limitation of not having IPv4 addresses again and will have to move to IPv6.
This might lead to pain and costs but I don't expect the world falling for that.
How IPv4 could explode in the '90s, so can IPv6. Let's look and see what we can do..
WHOOOSH
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
... since the unexpected end of the century in '99.
(What is actually surprising is that the internet still hasn't widely adopted IP6, and ISPs are now turning to ludicrous measures - NAT - to keep avoiding what makes sense.)
NAT actually *makes* sense for many interested parties. You get some protection from consumers using their connection to actually (*gasp*) serve stuff which, along with asymmetric connections and anemic upload bandwidth, keeps the ability to offer and publish and distribute things out of the hands of the masses and in the hands of the deserving few. Allowing consumers to reach out and consume stuff is good, allowing them to serve things and to be able to connect to each other isn't.
IPv6 is a technical solution to problems nobody who counts likes to see solved. NAT'ing the hell out of the consumer-facing side of the Internet creates something that is good enough for consumers and so much more suited to stuff that ghost called "Internet with billions of servers and peers on desks and in bags and pockets" back into the bottle.
I love how people on Slashdot like to throw around migrating to IPv6 like it can be done in a fortnight.
Migrating to IPv6 will cost ISPs BILLIONS. It is not simply a matter of flipping a few routers. It is tens of millions of lines of company code all geared around IPv4.
It is hundreds of millions of lines of third-party code that they have bought all geared around IPv4. You know, the software that RUNS THE INTERNET.
It is something that will take years to fully be completed, even though it has already been going on for years.
It is not the flip of a switch.
I work for one of these third party software companies so I know what I am taking about. To put it simply, the migration of our software 100% to IPv6 will take years to be fully done - and that is given a very large and capable team. This is not simply a matter of changing an int to two doubles and recompiling, it is a lot more complicated than that.
...runs on many cheap router platforms and allegedly is happy to do IPv6. The current Apple base stations also have two DNS entries set aside for IPv6 and another two DNS entries for IPv4 hosts. Another option is to repurpose an old laptop or mini to run any number of the open-source DNS servers out there and use that machine also to NAT, etc. Running your own DNS server has the additional benefit of speeding up lookups tremendously. But it is work and it consumes power... hence of marginal benefit unless you have a media server already running 24/7 and/or a craptastic provider like Comcast, whose DNS servers aren't all that reliable.
So, I keep hearing all this news about them running low... What happens when we run out?
At that point essentially anyone wanting a new block of IPv4 addresses for their domain is out of luck. In this case they are left with two choices:
- Move on to IPv6 for their servers
- Get someone else to host their services - with HTTP you can share an IP, but have a different name (requires virtual domains with the same server instance)
Both have limitations, since in the first scenario you are limited to IPv6 clients and in the second you are limited to what can be hosted.
In both scenarios you could get a single IPv4 address for you network and then just NAT the PCs.
As you can see the real limitation is not for those accessing services, but for those providing services. There is an extra issue that comes into play, for the the entity providing the online services: you will be forced to find an ISP who already has native IPv6 support or using and IPv6 tunnel.
Jumpstart the tartan drive.
And therefore it will be a perfect day to be celebrated in future. Lets say January the 2nd can be a nice day for IPv4-exhaustion. However, I hope it will take a little longer for that as I would prefer such day in summer so I can lie drunken under a tree without serious danger to my health (other than the alcohol) .
Yes I know this is a little bit egoistic as it is northern hemisphere centric view, but most people life north of the Equator ...
And yes I know the world changes on a daily basis, so the world as we know it ends every day.
Addresses are assigned to the RIRs by the Internet Assigned Numbers Authority, NOT the Internet Corporation for Assigned Names and Numbers. I know, all of these acronyms made up of Is, As, and Ns blur together.
Like how UTF-8 was designed to be backward-compatible with ASCII, because the first block of UTF-8 characters match those of ASCII?
I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
The summary sounds like the minutes from a Cylon board meeting
(1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
Really? You mean unclaimed right?
We are a decade away from needing to move to IPv6. Millions of IP Addresses are not used today or are still used for all the nodes in an environment. Most ISPs are nowhere close to using all their IPs. So while there are few unclaimed blocks of IPs, there are plenty of claimed but unused IP addresses.