71–80 of 131 posts
Earlier quoted context omitted.
Comcast and Verizon Wireless rolled out IPv6 years ago, and resolves IPv6 addresses first by default. Nobody is dicking around, it's just transparent.
How does that explain the massive spikes on weekends?
Earlier quoted context omitted.
I guess it's hobbyists who's normal internet connection is ipv4, but on the weekend they have time to dick around with ipv6 devices and connections.
Comcast and Verizon Wireless rolled out IPv6 years ago, and resolves IPv6 addresses first by default. Nobody is dicking around, it's just transparent.
Well, I am. Now let met enjoy my statistical insignificance !
Earlier quoted context omitted.
Not much! Just a few bytes for each packet. Running a NAT service requires a big table of all the active connections, ie. it's stateful - IPv6 with no NAT needs no per-connection state in the router so that's a big space-saving.
So you don't want stateful inspection on your private LAN router? Its ok for every hacker to portscan the 100's of IoT devices in your house? You're a very trusting fellow.
I've not run into a problem solved by IPv6. There's no incentive for ISPs to provide good service, so they can just follow the mobile carrier route and nat/proxy when exhaustion becomes an issue. As other countries go IPv6, more IPv4 addresses become available for the big cloud providers.
I get better peering though the HE tunnel broker than I get on IPv4. :)
I noticed the other day that IPv6 growth is slowing down, as Google measures it. Its access share used to double every ten or eleven months, now it doubles more slowly, and seems likely to reach 20% only in 2017 instead of this year, and if it goes on as in the recent months, 30% in 2018 instead of in 2017. At a guess, many of most competent ISPs have done their thing and now we're seeing the more sluggish middle. Or…
Here in France, there have been leading ISPs (Free ADSL), good citizens (SFR), and laggards that keep on dragging their feet (Orange, Numericable). Things got worse when Numericable bought SFR, halting progress with stupid rules in place that when you get the budget version of a contract you don't get IPv6 because reasons. Let's not get started on "pro" versions where you just don't get IPv6 at all, ever, and on the…
Earlier quoted context omitted.
Not much! Just a few bytes for each packet. Running a NAT service requires a big table of all the active connections, ie. it's stateful - IPv6 with no NAT needs no per-connection state in the router so that's a big space-saving.
So you don't want stateful inspection on your private LAN router? Its ok for every hacker to portscan the 100's of IoT devices in your house? You're a very trusting fellow.
IoT devices, if I had any use for them, would go on my private LAN. My private-public router can do complex stateful tracking, because it only has to handle a few connections at a time. Meanwhile my grown-up internet devices go on the public side and get actual internet access, meaning that e.g. two people inside my house can play an online game with a person outside my house, and aren't slowed down by a complex connection-tracking router. Also means my guests don't get access to my IoT devices.
IMO the major thing holding back IPv6 on the web is amazon. A huge proportion of services are hosted on AWS, and the lack of IPv6 addressing of instances cannot be forgiven.
Also I have servers in colocation with two datacenters, and for both I had to ask to the support to get an IPv6 range. We are very far from IPv6 becoming a standard feature.
Earlier quoted context omitted.
Here in France, there have been leading ISPs (Free ADSL), good citizens (SFR), and laggards that keep on dragging their feet (Orange, Numericable). Things got worse when Numericable bought SFR, halting progress with stupid rules in place that when you get the budget version of a contract you don't get IPv6 because reasons. Let's not get started on "pro" versions where you just don't get IPv6 at all, ever, and on the…
Is Free still doing 6to4 (which was probably fine at the time) or did they start doing native ipv6?
IMO the major thing holding back IPv6 on the web is amazon. A huge proportion of services are hosted on AWS, and the lack of IPv6 addressing of instances cannot be forgiven.
IPv6 and a return to end-to-end addressing isn't really aligned with the AWS style of proprietary platform lock-in.
"End-to-end addressing" is typically an end user issue, where end users use NAT. In the early days of the internet, nobody used NAT.
I check the google stats[0] on ipv6 adoption every few months. Last time I checked it was barely 9% an now it's on 15% ! I would have never thought we'd get this far this fast. Looks like the switchover is actually going to happen. [0] https://www.google.com/intl/en/ipv6/statistics.html
Really interesting how it spikes on weekends! I wonder if this is because more home broadband connections are ipv6-enabled compared to businesses?