News for hackers. Stuff that matters.
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by IgorPartola on Thursday May 22, 2014 @06:23PM (#7786925)
So there is a lot of sentiment that I've been hearing over time about when exactly will IPv6 become a thing. Here's how I see it:

Step -1: We started running out of IPv4 addresses. The internet is IPv4-only for all practical purposes. Nobody is doing IPv6 because it's still experimental. Your weird neck-bearded friends are talking about it, that's about it.

Step 0: Inception! IPv6 is now a standard and you can route IPv6 over the tubes. Two networks have connected!

Step 1: Dual stack is a thing. Now you can set up both IPv4 and IPv6 on the same network and they co-exist. Some hosts (goole.com, facebook.com) try this and finally turn it on for good in 2012.

Step 2: Dual stack intensifies. This is where we are now. You cannot yet run a full blown IPv6-only network that you want to talk to the Internet and do anything practical with it, but all your cleanly shaven friends are now telling you that you should support IPv6 first, then add IPv4 for compatibility. Google sees as much as 3.5% of their traffic over IPv6.

Step 3: The cost of any single IPv4 address rises dramatically. For an end user it's already roughly $1/month. Buying in bulk is much cheaper, but not free like it used to be. ISP's and other service providers (Amazon, Rackspace, Digital Ocean) are going to start noticing the costs on their bottom lines. Severe restrictions are imposed by IPS's and service providers on anything but the bare minimum of IPv4 usage.

Step 4: The future. The first IPv6-only networks start to pop up. They use special network translation to talk to IPv4-only internet. (You can do this at home now! It's called NAT64: http://www.litech.org/tayga/).

Step 5. The number of IPv6-only networks is growing rapidly. IPv4 is now a legacy protocol. All your friends are telling you that they cannot believe we are still using IPv4 and how much of a pain it is to support it. Sales of T-shirts with "There is no place like 127.0.0.1" drop dramatically.

Step 6. The same people that put together IPv6 World Launch Day put together an IPv4 funeral. Major companies turn off IPv4 presence.

The crucial point here is not that someone demands IPv6 by calling their ISP, etc. It is fun to play with and you should at least get a tunnel set up through Hurricane Electric if you are reading this, but the demand here does not matter. What matters is supply: supply of IPv4 that is. Once that goes to nil, the cost rises and some executive at every ISP and service provider has a bright idea to save the company millions by switching everyone to IPv6. That's it. We, the people in the trenches, cannot affect this. We cannot speed it up and we cannot slow it down. The invisible hand of the market will make IPv6 happen all on its own.

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by wyager on Thursday May 22, 2014 @09:43PM (#7787619)
> Sales of T-shirts with "There is no place like 127.0.0.1" drop dramatically.

The nerdy t-shirt industry experiences a boost in margins, as they can now save ink by printing the much shorter "::1".

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by lambda on Thursday May 22, 2014 @11:33PM (#7787847)
The sad part about IPv6 is that there's only one loopback address; ::1.

In IPv4, you have an entire /8 at your disposal, just for talking to yourself!

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by simon_vetter on Friday May 23, 2014 @12:24AM (#7787968)
Aside from ::/128 (undefined address) and ::1/128 (local loopback), the entirety of ::/96 was reserved for ipv4-compatible addresses and had been deprecated for a while [1]

It is safe to assume that they won't be allocated in the future. You can easily assign them to your loopback interface. e.g. on linux:

  $ ip addr add ::2/128 dev lo
You will then be able to use them over loopback just like ::1, and can populate your /etc/hosts file accordingly.

  $ ping6 -c 1 ::2
  PING ::2(::2) 56 data bytes
  64 bytes from ::2: icmp_seq=1 ttl=64 time=0.078 ms
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.078/0.078/0.078/0.000 ms
[1] http://tools.ietf.org/html/rfc4291#section-4

EDIT: formatting.

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by blueskin_ on Friday May 23, 2014 @09:17AM (#7789165)
>Sales of T-shirts with "There is no place like 127.0.0.1" are replaced by "There is no place like ::1".

FTFY.

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by avis on Thursday May 22, 2014 @08:17PM (#7787368)
Are we currently in step 3? How much does a /24 running for right now?
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by IgorPartola on Thursday May 22, 2014 @09:53PM (#7787636)
We are between step 2 and 3. Looks like a /22 is $500 currently: https://www.arin.net/fees/fee_schedule.html.
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by lambda on Thursday May 22, 2014 @11:37PM (#7787860)
Hmm. I would argue that we're still in step -1, though the clean shaven folks have finally started listening to the neckbeards in a few circumstances and are slowly moving around towards step 0.

Most people still can't actually route IPv6 over their tubes without going through a tunnel broker. At least for home, small office, and companies that aren't tech heavy, it's still firmly in the neckbeard camp.

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by IgorPartola on Friday May 23, 2014 @12:00AM (#7787912)
Well, you definitely can route IPv6 over the public backbone. If you get an IPv6 address in SF and I get one in NYC, we can already talk to each other. That is how we got past step -1. Dual stack is now a pretty standard setup on a non-trivial, though still small number of networks. For example, Linode, Comcast, T-Mobile all support dual stack on at least some of their networks.

What we have not quite reached yet is the point where IPv4 addresses are really expensive. You still get one with every VPS you sign up for and with every home connection. Once that can no longer be done, IPv6 will become standard pretty much across the board, starting in Step 3 and 4.

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by danyork on Friday May 23, 2014 @06:37AM (#7788727)
As another example, when I am using LTE on Verizon Wireless, I am connecting over IPv6 to sites running IPv6 (ex. Google, Facebook, Wikipedia, etc.). I can go to sites like http://www.test-ipv6.com/ and see that I have full IPv6 connectivity.
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by lambda on Saturday May 31, 2014 @04:53PM (#7827238)
Hey, so I had posted the above primarily because I've been trying to get a routable IPv6 address for a while, and haven't been successful; I've repeatedly asked Comcast when my CMTS would be IPv6 enabled, but their techs have just said "try enabling IPv6 on your computer and see if it works", they haven't been able to give me a schedule or even tell me if it was supposed to work yet.

However, just checked last night and discovered that they'd added a new feature that would tell you when your CMTS was IPv6 ready, and it turns out that they've finally upgraded me. I could finally switch off my tunnel and use a real, routable address. Woo!

Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by kivikakk on Friday May 23, 2014 @06:12AM (#7788681)
Major (consumer) ISPs in Australia offer native dual-stack.
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by jimmcslim on Friday May 23, 2014 @07:49PM (#7791997)
Which ones? I'm with iiNet and was wondering if they offered it yet but couldn't see anything about it online.
Re:Goodbye, IPv4 IANA Starts Allocating Final Address Blocks by avis on Thursday May 22, 2014 @10:01PM (#7787652)
Yeah, but thats only for those who meet the requirements. The Real world scenario is that people pay about $500/mo for a /24 I heard - kind of a black market thing.