Latin America Exhausts IPv4 Addresses
An anonymous reader writes "LACNIC, the regional Internet registry for Latin America and the Caribbean, considers its IPv4 address pool exhausted, because it is down to less than a quarter of an /8, roughly 4 million IPv4 addresses which are reserved for facilitating transitioning mechanisms. Half of those addresses will be assigned on a first come, first served basis, but no more than 1024 addresses per organization every 6 six months. Allocations from the last 2 million addresses will be a maximum of 1024 addresses total per organization. To maintain connectivity, it is now indispensable to make the switch to IPv6. LACNIC's CEO expressed his concern that many operators and companies still haven't taken the steps needed to duly address this circumstance. The RIRs for Asia-Pacific, Europe and North America have all imposed similar limitations on IPv4 assignments when they also crossed their local exhaustion thresholds. As of now, only AfriNIC is not in address exhaustion mode."
Joining North America, and Europe/the Middle East/Central Asia.
So they're only allowing organizations to have 1024 addresses per three years?
We warned you years ago this would happen! But no-one ever listens.
For years, indeed. I think it was 14 years ago, in 2000, on April Fool's day I announced on a major forum that the internet would be down for about 20 minutes while the root nameservers were switched over to IPv6.
This sounds like Y2K all over again...
If Pandora's box is destined to be opened, *I* want to be the one to open it.
They've basically already did this with ipv6 with all the ipv4 numbers accessible as a subset of ipv6.
I don't see the adoption of an area code system any more likely than the adoption of ipv6.
There might be some type of solution like that though. Basically what you're suggesting is allowing 2
computers to have the same ipv4 address so just like 2 computers not on the same network can
have the same mac address without conflicting it could be possible to design a system where a
computer in africa has the same ip as a server in china without conflict.
Surprisingly, Comcast is now giving out /64 IPv6 addresses in my area (south-eastern Massachusetts). Spent a couple of evenings last week getting it all connected. Works fine.
Let us know when it gets down to zero available and then we'll spend the weekend fixing it.
If we're too lazy to switch to ipv6 then they need to just start charging per ip.
$1 per ip per year should be sufficient to cause plenty of ip hoarders to return their stock.
If that's not enough then increase it to $1 per ip per month. Still small enough that
it shouldn't really affect anyone too much. My guess is any computer that can't
absorb a $1/month charge is not an actually computer and should have a private
10.0 number anyways.
Charge per ip might also be a good way to help encourage ipv6 switchover.
I can remember number.number.number.number.
I cannot remember ASDFDAVUDSFWSNASDCNACKEFADCKSA Which is also an IPV6 address
It's like instead of adding an area code to the phone system, we add letters of the alphabet such that my phone number is now 123-456-7890-ABCDEF-GHIJKLMN and then people no longer can remember phone numbers and refuse to use it.
All IPV4 needed was another octect or two TOPS.
I can easily remember 10.0.0.0.1 as my new local 5-octet private subnet. But jeeze don't just add 500 alphabet characters expecting things to be the same.
You know that's just hex code right? IPv6 addresses can also be written in decimal if you want. IPv6 really is just like adding an area code to the IPv4 addresses.
I'm pretty sure the letters are limited to A-F and map to hexadecimal notation. Not arguing that it's any easier to remember than you suggest but it's not the whole alphabet being used here. IPv6 addresses can be expressed in decimal (or octal for that matter) but the reasoning behind using hexadecimal notation is that it reduces the number of 'digits' you need to remember. It's easier to wrap your head around it if you've ever used hex for memory addressing or similar low level tasks.
Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
Not saying it's not possible but all of the cable modem they've put out that is IP6 compatable has it's IP6 disabled, I've feeling there are going to be a lot of accounts on one address (Nat) style.
Not that disappointed, using a HOSTS file and working with IP4 address I've a bit of sense about them, IP6 I couldn't tell you if I've seen it before or not, age does play a bit into this/
IPv4 brokers exist, and their main function is to facilitate address block sales.
Google "ip broker" (and ignore the "intellectual property" hits).
The problem is that people were fear mongering the imminent exhaustion of IP 4 addresses for 20+ years. We were supposed to run out in 1992.
Eventually people will dismiss your warnings because you were not realistic about them in the first place. Now that it is happening, no one is paying attention until the whole thing comes to a screeching halt.
I recently upgraded my old DSL to Uverse (with one of the newer Motorola modems, not the 2wire modems that I hear were total crap in comparison), and they have 6rd allocations set up for their IPv4 space, using a 24-bit 6rd block. So not only can I access the v6 internet, my 6rd address block is static based on my static IPv4 address block. (At least if and until they decide to more their customer addresses into a "real" IPv6 allocation.) As I understand it, the modem itself does the 6to4 encapsulation to ATT's outbound IPv6 proxy.
So IPv6 is finally reaching at least some regular ISP customers.
#naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
Does every cellphone, toilet, refrigerator, atm, medical device, desktop terminal, etc etc etc really need a public IP address?
How else do you expect the NSA to track them?
1024 per 6 months per organization.
So what will organizations do? Right. Reserve 1024 IP addresses every 6 months, need them or not, because they MIGHT need a few 1000 down the road at some time. Chances are they don't, but "just in case".
Our government tried to limit water use by cutting off water supply whenever it got scarce. Can you imagine how much water got wasted? The reason is simple, people filled every kind of container (bathrub, sinks, buckets, even coffee cups) whenever water was available, only to drain it whenever water got available again to refill with fresh water...
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Do like I did, get a free 4to6 tunnel from tunnelbroker.com, a public service from Hurricane Electric (he.com). Since my edge router is able to run the Tomato firmware, it has the capability to act as the endpoint for one of these tunnels, plus it can update my dynamic address from Cox when it changes, to keep the tunnel working.. Very slick.. Its fun to watch my Debian machines doing an apt-get update, and seeing an ipv6 address listed.. The current version of Tomato also implementts ip6tables so you're protected from that end.. Even if you don't have an edge router that can do Tomato, its still pretty easy to configure an always-on Linux machine to handle the tunnel endpoint, just so long as your firewall can be configured to pass protocol 41 (6to4 protocol, as I recall).. They give you a /64 prefix, which is a multi-mega-bazillion number ipv6 addresses.. Big numbers like that give me a headache..
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
So why doesn't the NSA pump money behind IPv6 rollout?
If there's one organization that SHOULD have an interest in (virtually) unlimited unique IP addresses that allow tracking every single device using one, it's them.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Price = demand / supply There will never be IPv6. If it's up to market.
These kinds of stories have been popping up on Slashdot for a while, but I note Slashdot *STILL* doesn't have an IPv6 address even though it's a site supposedly run by and for technologists. Meanwhile, Facebook, a site made for teenagers to post selfies on, has had IPv6 support for three or four years.
Oolite: Elite-like game. For Mac, Linux and Windows
One of the problems with IPv4 address exhaustion is that routing tables become very complex. Having everyone try to glom a dozen random /24s together to make their local networks will not help.
Also, this is an exponential growth situation, so stopgap measures won't buy much time anyway.
Visit the
That problem is shared by people all over the globe.
And even if your ISP offers v6 support, they often "forget" to tell their support. If yours offers v6, if you have some spare time and want some entertainment on support's expense, call them and ask them for aid in setting up v6.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
So ... you say that we should adopt v6.
Because that's essentially what adopting v6 would be about.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Waiting for IPv7, I hear its going to be much better.
> As of now, only AfriNIC is not in address exhaustion mode."
That is not true - ARIN (north America's RiR) is still handing out IPv4's and will continue to do so until down to their last /10.
https://www.arin.net/resources...
So an address like C0A8:0166 is not to your liking? Would you like 192.168.1.102 better? Or are you the kind of decimal purist that would feel more comfortable with 3,232,235,878?
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Kinda how IPv6 works; except there's only one two-octet area code (2002::, or 32.2. in dotted decimal) for the old IPv4 addresses, and all the other addresses work differently.
(Of course, if the recipient only understands IPv4, and the sender only has an IPv6 address, then the packets can only be sent one direction. I'm not sure if or how an IPv6 host and an IPv4 host can establish a TCP handshake, starting from either end.)
I keep checking their site to see if they've started supporting my part of town. Still no love.
Your explanation is good, but I agree with the sentiment expressed by the OP. I don't have a problem with hex, per-se, but I have a harder time memorizing MAC addresses (or IPv6 addresses) than IPv4 addresses.
The decision to switch from decimal to hexadecimal notation was arbitrary and jarring...not at all unlike switching phone numbers from decimal to alphanumeric notation would be.
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law
It's still quadrupling the information (from 32 bits to 128 bits), though most IPv6 addresses can be shortened.
But to be honest, this is what DNS is for. If you find yourself regularly having to memorize or manually type dotted quad IPv4 as a user, you're doing something wrong; and if you're a sysadmin, you're routinely memorizing (or writing down) other things that are more complex than that.
Mnemonics could also help, like assigning words to bytes.
Not really. An area code, in the US and Canada at least, is 3 digits. Going from IPV4 to IPV6 adds a lot more than 3 digits. An actual example of an IPV6 address is as follows:
2001:0db8:85a3:0000:0000:8a2e:0370:7334
which is a lot longer than an IPV4 Address such as:
123.123.123.123
And IPV6 address has 4 times as many digits as an IPV6 address, if you write it in the same base. That's way more than just adding and "area code"
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
I can remember number.number.number.number.
I cannot remember ASDFDAVUDSFWSNASDCNACKEFADCKSA Which is also an IPV6 address
I can easily remember 10.0.0.0.1 as my new local 5-octet private subnet. But jeeze don't just add 500 alphabet characters expecting things to be the same.
You seem to not realise that IP6 has shorthand built in.
For example the IP6 address of Wikipedia is 2001:503:BA3E::2:30, not really that much harder than 91.198.174.192 is it?
Local subnets are even easier, fe80::1 is actually shorter than 10.0.0.0.1
This is a solved problem. As one of the smartest and most knowledgeable computer experts in the world, Stephen Fry, has said, all they need to do is register a .uk domain to generate new IP numbers.
.idiot
if this is supposed to be a new economy, how come they still want my old fashioned money?
The decision to switch from decimal to hexadecimal notation was arbitrary and jarring...not at all unlike switching phone numbers from decimal to alphanumeric notation would be.
I'm not so sure. Data entry is, IMO, much more difficult when dealing with hexadecimal, but memorizing the strings actually seems easier to me, or at least on par. Some example phone numbers:
18003368478 -> base36 = 89qqo0u
18003569377 -> base36 = 89quz1d
7185551212 -> base36 = 3au3ass
base36 is unrealistic, but so is the phone number comparison. IP's are dotted quads; phone numbers are normal base 10 numbers.
216.34.181.45 -> decimal = 3626153261 (which is, IMO, harder to remember... not that anyone memorizes more than a couple IPs)
216.34.181.45 -> hex = d8.22.b5.2d (which is, IMO, just as easy, if not easier, to remember)
base36 = 1nyx1rh
The reason you have a harder time memorizing mac addresses is probably because they contain more information than IPv4. Ex:
00:16:3E:02:90:52 -> IP like notation = 0.22.62.2.144.82 (seems just about as hard to remember IMO).
An actual example of an IPV6 address is as follows:
2001:0db8:85a3:0000:0000:8a2e:0370:7334
That is not an actual example of an IPv6 address. Lets try with some real examples instead:
google.com has IPv6 address 2a00:1450:4005:801::1007
gmail.com has IPv6 address 2a00:1450:400f:803::1016
facebook.com has IPv6 address 2a03:2880:2110:df07:face:b00c::1
arin.net has IPv6 address 2001:500:4:13::124
arin.net has IPv6 address 2001:500:4:13::125
ripe.net has IPv6 address 2001:67c:2e8:22::c100:68b
gigabit.dk has IPv6 address 2a00:7660:0:50::2
The last one is my own website. Your IPv6 address is as long as you want it to be. Many ISPs will assign you a /48 prefix, which is just 16 bits more than your IPv4. It is literally just an area code more (two bytes). What happens with the last 80 bits is up to you. You can make them all zero if you want to. And since all zero can be shortened to "::" that all just goes away.
As to those first 48 bits there is a system in it, which makes it easier to remember. Notice how all of the above has either 2001 or 2a0x as the first block? Also the second block is the ISP and most people only deal with a few of those. So you will quickly memorize that. The third block is basically your customer id within the ISP. And everything after that is yours to decide.
It is true that if you go with auto configuration addresses on your computer, you will get horrible long addresses. But if you are doing that, you are not the kind of person to deal with IP addresses. Personally I let my computer choose any long address it want, but for my servers I am picking something sane.
It's world cup. big titted groupies and cheap beer. screw this internet shit.
Why has people not generally adopted V6 years ago ?
It's simple ... IPV6 is not simple.
It is a complicated piece of work, trying to please everybody. Crypto,Traceability, cryptic syntax ect. ect.
Somebody should design ipv8, an 8 byte adress ipv4 version with none of the ipv6 crap - release it and watch it getting adopted in less than a year ....
Like forcing IPv4 to stay in country only. If you want to go to a server in another country, you have to get there via IPv6.
Or give each country a IPv4 address range, but certain addresses are reserved for international servers. Multiple IPv4 networks that overlap on addresses that are outside the country.
Right...I get the pro-change argument, I just (still) think it was arbitrary and jarring.
It may seem trivial, but something as simple as keeping the decimal notation would probably have gone a long way in spurring adoption of IPv6.
I know that representing numbers in hex doesn't make them different, and takes up less screen real estate, but they *look* different. I think everyone talking about reasons for low adoption vastly underestimates the psychological impact of the way addresses are represented in v6.
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law
IPV6 is like the iPhone *c and *s models that everyone skips while waiting for the next version -- not enough new features, the current one is good enough, and "polycarbonate" doesn't that just mean "plastic"?
-- I was raised on the command line, bitch
mmm... just end them in CAFE:BABE:xxxx and start at 0, easy to remember :)
Also, face:b00c... really? but I guess it makes it easy for them to remember.
The transition to IPv6 is happening already. Lots of people have it without even knowing and newer consumer hardware is able to support IPv6 without any issues. It's already getting to the point where some ISPs are NATing their users for IPv4, but giving them IPv6 addresses. Some are even doing strange things like converting IPv4 traffic to IPv6 if an AAAA record is available for a site.
+1, score this post up
I refuse to sign
Why has people not generally adopted V6 years ago ?
Probably because the hardware in (almost) every routing device needs to be updated to support it. Even if you went with a simple expansion of IPv4 it wouldn't be simple because a router that's looking for a 4 byte address isn't going to know what to do with an 8 byte address. Might as well go with a 16 byte address while we're updating everything.
I recently switched from FiOS to Comcast and was pleasantly surprised to see my router giving out IPv6 addresses to all the computers on the network. Somewhat surprising that Verizon doesn't support it even though they have the newer networking technology.
Surprisingly, Comcast is now giving out /64 IPv6 addresses in my area (south-eastern Massachusetts). Spent a couple of evenings last week getting it all connected. Works fine.
Emphasis added. Until the freebie routers start handing out IPv6 blocks by default and routing IPv6 traffic cleanly, this will never work. Why on earth would you need to actually do any work by hand?
You're special forces then? That's great! I just love your olympics!
I never use my IP address why would they? maybe they can put Latin America on its own private lan.
I can't imagine connectivity to Europe, the US or Australia would be particularly good from anywhere other than Egypt.
Why do you need IPs? They aren't hard to get if you have a actual reason. (I'm a owner of a /24)
IPv6 is an extension of IPv4. You can't extend IPv4 without giving it a new version number, the most you can do is add some protocols layered on top of it or tunnel through it.
Any ping program that can deal with an address longer than 32-bits is inherently incompatible with IPv4 ping protocol. Now it is true that you could write a single ping program that can deal with both IPv4 and IPv6 simultaneously.
But do you need to remember it? Your computer needs to remember it but there's not much practical need to memorize it yourself.
Hmm, my uverse won't do ipv6 and the problem seems to be the router.
That would be part of the jarring change I'm referring to, yes.
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law
I just moved, got comcast, hooked up my modem & router (brought my own, but reset to factory defaults before install) and got ipv6 out of the box. No mucking about needed.
Not a sentence!
ICMPv6 != ICMPv4
CLI paste? paste.pr0.tips!
The problem with IPv6 is that it is *not* an extension of IPv4. Instead, it is a "second system syndrome" monument to itself, which entirely explains why it has so far not succeeded in spite of immense hype and effort. The dumbest feature of IPv6? 128 bit addresses instead of 64. But the list just starts there.
When all you have is a hammer, every problem starts to look like a thumb.
Well, actually, my system is a bit special. There's a Linux box acting as a firewall/router at the front-end, for a start, and that's why I had to spend extra time setting it up. As other people seem to be reporting here, normal setups seem to work without additional screwing around.