Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
The Internet

Latin America Exhausts IPv4 Addresses 197

Posted by Unknown Lamer
from the bofh-excuse-#666-internet-ran-out-of-addresses dept.
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.
This discussion has been archived. No new comments can be posted.

Latin America Exhausts IPv4 Addresses

Comments Filter:
  • Slashdot (Score:5, Informative)

    by Alioth (221270) <no@spam> on Wednesday June 11, 2014 @11:18AM (#47213173) Journal

    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.

  • by AdamHaun (43173) on Wednesday June 11, 2014 @11:20AM (#47213201) Journal

    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.

  • by sjames (1099) on Wednesday June 11, 2014 @01:55PM (#47215375) Homepage

    Case in point - everything will again have their own IP address and you don't have to use stuff like STUN or other things because end-to-end connectivity is guaranteed. False, since firewalls are still around, and just because both ends can see each other doesn't mean they can talk to each other.

    So open the needed port in the firewall. No more STUN.

    Then there's the "guilty PC" problem that the content creators oh-so-love. It's hard to identify people from PCs now because so many devices share a single IP address. But when that single IP means a single device, it's a heck of a lot easier.

    So pick another address at random. You have 256 IPv4 internet's worth to choose from within your prefix.

    Well, with IPv6 right now, if your ISP changes your prefix, have fun resetting the configuration of everything to use that new prefix. Hope the auto-discovery picks everything up and maybe things will work. If not, have fun debugging. And while NATv6 is defined, many places (e.g., Linux) refuse to accept it. I mean, is it so bad that my internal network ... works? And if my ISP gives me a new prefix I do diddly squat like right now? Or that I don't have to remember what the IP is of the PC next to me is after it's prefix changes?

    Use the local prefix to talk to local machines. Use autoconfig to handle the ISP assigned prefix. It actually does work. There you go, zero work.

  • by AndroSyn (89960) on Wednesday June 11, 2014 @02:09PM (#47215521) Homepage

    His point is, slashdot doesn't even have an IPv6 address, he's using 6to4 NAT and can still reach the site. The IPv4 address for slashdot is embedded in the IPv6 address.

    $ ping6 slashdot.org
    PING6(56=40+8+8 bytes) 2001:8b0:ca12:3193:7dc2:1078:67fb:31f4 --> 2001:8b0:6464::666:616:d822:b52d
    16 bytes from 2001:8b0:6464::666:616:d822:b52d, icmp_seq=0 hlim=241 time=165.418 ms
    16 bytes from 2001:8b0:6464::666:616:d822:b52d, icmp_seq=1 hlim=241 time=121.267 ms

    The IPv6 address he was pinging was as follows: 2001:8b0:6464::666:616:d822:b52d

    The d822:b52d in the IPv6 address, is actually the IPv4 address for slashdot:

    d8 = 216
    22 = 34
    b5 = 181
    2d = 45

    $ host -t a slashdot.org
    slashdot.org has address 216.34.181.45

    Make sense? ;)

Hold on to the root.

Working...