Live data from Hacker News

IPv6 Adoption Statistics

google.com

31–40 of 134 posts

Re: IPv6 Adoption Statistics

#31

Can IPv6 become, ironically, the reason ipv4 never dies? Once a majority move to v6 wouldn't that mean a whole bunch of the ipv4 space is being free'd up. This allows those who never update to actually never update.

But if a majority move to IPv6, wouldn't the holdouts have difficulty communicating?

There has to be bridges to IPv4. There will be IPv4 only servers for a long long long time.

Re: IPv6 Adoption Statistics

#33
post #29
post #26

Earlier quoted context omitted.

While having an unique address per application can be cool, I don't like the premise that this is used as some sort of security layer. We have firewalls. We know how they work and how to implement them well. For all intents and purposes a typical NAT-setup is bascially wide open from the inside and out. You can do the same with a few simple rules on a firewall.

I know we have firewalls, but in the normal desktop use-case, there are some applications that you want to be able for external clients to connect to. Skype (or other VoIP clients), Bittorrent, Game servers, etc all work better with or flat-out require external connectivity. In the V4 world, we have upnp or NAP-PMP to allow applications to open a port on the router and to have the router then forward the packets to a…

[deleted]

Re: IPv6 Adoption Statistics

#34
post #29
post #26

Earlier quoted context omitted.

While having an unique address per application can be cool, I don't like the premise that this is used as some sort of security layer. We have firewalls. We know how they work and how to implement them well. For all intents and purposes a typical NAT-setup is bascially wide open from the inside and out. You can do the same with a few simple rules on a firewall.

I know we have firewalls, but in the normal desktop use-case, there are some applications that you want to be able for external clients to connect to. Skype (or other VoIP clients), Bittorrent, Game servers, etc all work better with or flat-out require external connectivity. In the V4 world, we have upnp or NAP-PMP to allow applications to open a port on the router and to have the router then forward the packets to a…

Isn't it easy enough to just have a local firewall on each machine where you open up ports for the apps you want to be public?

Re: IPv6 Adoption Statistics

#35
post #24

After I switched ISP to one that supports native IPv6 (and generally is pure awesome), I noticed that my traffic at home went to about 50% IPv6, also thanks to YouTube supporting V6. I also casually noticed that all but one address in my "Account Activity" view in Gmail are IPv6 addresses (ironically, the mobile phone got the one single IPv4 address in that list over 4G). V6 works nicely and totally transparent causi…

> One thing that's tricky about V6 is the fact that without NAT all your boxes are internet-reachable unless you have a firewall. That's easily added of course, but whereas we have protocols like upnp and nat-pmp to reconfigure NAT routers, there's nothing equivalent for various applications to tell the router to forward some V6 traffic.

Is there any reason the same approach shouldn't work? All the application needs to tell the router is "please open this inbound port on this address", right? Like, in theory couldn't a router just follow the existing uPNP/nat-pmp standards and do the right thing with those messages?

> That way, I could theoretically get away without a restrictive firewall while still giving applications a way to be directly connected to. An attacker would have to scan a /48 (in my case) or a /64 (in the worst case) in order to find an open port given a known remote address.

I think that's a terrible idea. An attacker could e.g. sniff packets inbound towards your network to figure out the address. Addresses are not designed to be secret or a security feature.

Re: IPv6 Adoption Statistics

#36
post #32

I'm curious about the peaks and troughs in the graph. It seems the graph reaches a peak every week, does anyone know a reason for this?

Weekends. More home users have IPv6 than business users. Comcast and Time Warner are both pretty far along in their IPv6-availability rollout.

(You can also check last Christmas, where there's a bit of an extended peak.)

Re: IPv6 Adoption Statistics

#38
post #23

Can IPv6 become, ironically, the reason ipv4 never dies? Once a majority move to v6 wouldn't that mean a whole bunch of the ipv4 space is being free'd up. This allows those who never update to actually never update.

People who adopt IPv6 addresses tend to keep an IPv4 address as well.

Until we see more carriers moving users over to DS-Lite, where their IPv4 usage is NATed https://news.ycombinator.com/item?id=8680759

Re: IPv6 Adoption Statistics

#39
post #32

I'm curious about the peaks and troughs in the graph. It seems the graph reaches a peak every week, does anyone know a reason for this?

Hehe this was an exercise question at my university. Look at the peaks again, zoomed in on a week, and you'll see that it's always on the weekend.

This most likely means that more people have IPv6 connections at home (weekend), than they do at their work place (throughout the week).

Re: IPv6 Adoption Statistics

#40
post #24

After I switched ISP to one that supports native IPv6 (and generally is pure awesome), I noticed that my traffic at home went to about 50% IPv6, also thanks to YouTube supporting V6. I also casually noticed that all but one address in my "Account Activity" view in Gmail are IPv6 addresses (ironically, the mobile phone got the one single IPv4 address in that list over 4G). V6 works nicely and totally transparent causi…

The protocol you're looking for is PCP which is the NAT-PMP successor that also works with IPv6: https://en.wikipedia.org/wiki/Port_Control_Protocol

Unfortunately it's going to take a while until it's widely supported.

Post reply on HN