Earlier quoted context omitted.
I run into NAT almost every single day. It wastes time, breaks things, consumes router resources, rules out certain technologies/products/services and duplicates so much work it's just unreal.
>consumes router resources Thats a weird claim to make against IPv4. Grab a calculator and see how much memory is required by a IPv6 /64 address space.
IAB Statement on IPv6
51–60 of 131 posts
Re: IAB Statement on IPv6
#52Earlier quoted context omitted.
I run into NAT almost every single day. It wastes time, breaks things, consumes router resources, rules out certain technologies/products/services and duplicates so much work it's just unreal.
>consumes router resources Thats a weird claim to make against IPv4. Grab a calculator and see how much memory is required by a IPv6 /64 address space.
Why am I trying to fill out in memory an entire /64? More importantly what purpose will doing that for a home network that will at best have 100 nodes even with ipv6? The memory needed to route and track 100 ipv6 nodes vs 100 ipv4 is a rounding error. Even if I enabled privacy extensions the amount of addresses is miniscule.
Nat sucks, end of story, and yes ipv6 requires more memory. It is a bigger address range after all. We also gain a lot of what we lost with ipv4 years ago.
Re: IAB Statement on IPv6
#53Earlier quoted context omitted.
Amazon seem to be slowly getting there: https://aws.amazon.com/about-aws/whats-new/2016/10/ipv6-supp...
ELBs support ipv6 as well
Re: IAB Statement on IPv6
#54Earlier quoted context omitted.
Really interesting how it spikes on weekends! I wonder if this is because more home broadband connections are ipv6-enabled compared to businesses?
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.
Re: IAB Statement on IPv6
#55Re: IAB Statement on IPv6
#56I'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 run into NAT almost every single day. It wastes time, breaks things, consumes router resources, rules out certain technologies/products/services and duplicates so much work it's just unreal.
Example: Verizon Wireless.
Re: IAB Statement on IPv6
#57I 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…
Let's not get started on "pro" versions where you just don't get IPv6 at all, ever, and on the phone you can even get them mumbling that it's not even on the table (Completel).
Re: IAB Statement on IPv6
#58Re: IAB Statement on IPv6
#59Earlier quoted context omitted.
Here in Japan, the largest consumer fiber wholesale network (NTT) "supports" IPv6, but you need a separate, $100 router that talks PPPoEv6 since none of the common consumer routers (including the one they provision you with) seem to support it. I also haven't been able to get PPPoEv6 working in macOS.
Anything that can run OpenWRT should be able to do PPPoE with IPv6.
Re: IAB Statement on IPv6
#60Earlier quoted context omitted.
>consumes router resources Thats a weird claim to make against IPv4. Grab a calculator and see how much memory is required by a IPv6 /64 address space.
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.