4 ms·

> IPv4 no longer exists I hope you're right, but i'm not entirely convinced. IPv4 has proven to very resilient. A survey in Denmark of pretty much all ISPs re

> IPv4 no longer exists I hope you're right, but i'm not entirely convinced. IPv4 has proven to very resilient. A survey in Denmark of pretty much all ISPs reveals that most, if not all, of the large ISPs have absolutely no plans for migrating to IPv6. Not as "not right now", but as "no plans at all". Some of them have plans for migrating business customers, but no plans for residential. We'll end up with companies running IPv6 and the rest of us stuck on an IPv4 network with a 4to6 gateway. https://ipv6-adresse.dk/ https://ipv6-adresse.dk/

soneil 7y ago
I asked my ISP, and got a template reply telling me they were shooting for late 2017. I asked again in 2018, and received a template reply telling me they were shooting for late 2017. I asked in 2019, and got the same reply ... They've since changed ownership, so I'm curious if the 2020 reply will still be late 2017.
FeepingCreature 7y ago
At least here in Germany, my ISP doesn't even give me a publically routed ipv4 by default anymore. Ipv6 no problem though.
p1mrx 7y ago
What actually is a 4to6 gateway? For example, how would an IPv4 client connect to a 128-bit address like 2606:4700:20::6819:6c0d?
- quintushoratius 7y ago
  You contract with a tunnel broker (most, if not all, are free) to give you an address. If you have a lan then you can set up radvd (or similar) to distribute addresses. You may need to replace your router though. Your ipv6 packets head out over a 4to6 tunnel to your broker, and then out to the wider world.
  - drdaeman 7y ago
    Nah, that's not the problem/solution, not in the ISP context. It's trivial for most ISPs (unless they have ton of ancient hardware and neglected to upgrade, or if they have very poor and limited peering options) to obtain an IPv6 block and set it up on their backbone network. All the complexity is about providing this to the end users. Depending on your tech stack, you may have no issues, or you may need to replace just about everything (NASes, accounting/billing system, etc - whatever pieces were built with IPv4-only in mind) Source: I worked for an ISP a while ago. We got our servers IPv6 connectivity, in, like, a day. We haven't solved IPv6 end-user connectivity (but it really wasn't a priority then), although was we had a few experimental connections - with lots of duct tape and random end-user issues whenever something was misconfigured (e.g. at the time not every site's AAAA record was actually responding, despite the existence).
- drdaeman 7y ago
  I can imagine a weird contraption of a custom DNS server that tracks client requests, returns unique private IPv4 addresses and simultaneously tells to some NAT-PT engine that this source IPv4 address talking to that destination IPv4 address needs to be translated to that IPv6 address. I can imagine this to be extremely fragile and break whenever an IP address is looked up using any different manner than plain DNS (e.g. by having IP in API responses, or just using DoH). Yet, I can imagine someone's probably already working on this abomination.
  - unilynx 7y ago
    Just return the same IP for everything and check the Host header or SNI name to know where to forward requests to It’ll work fine for web traffic.
- jotm 7y ago
  https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64 There's some other tools to facilitate that. FWIW, I tried playing with IPv6 on my home LAN. all IPv6 intranet, IPv4 on the ISP WAN, all ran fine on OpenWRT routers with a bit of configuration.
Symbiote 7y ago
See Google's statistics. Denmark has a low adoption rate in Europe, but that can change fairly quickly if a large ISP implemented IPv6. The world is at 26% adoption. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html

soneil 7y ago

I asked my ISP, and got a template reply telling me they were shooting for late 2017. I asked again in 2018, and received a template reply telling me they were shooting for late 2017. I asked in 2019, and got the same reply ... They've since changed ownership, so I'm curious if the 2020 reply will still be late 2017.

FeepingCreature 7y ago

At least here in Germany, my ISP doesn't even give me a publically routed ipv4 by default anymore. Ipv6 no problem though.

p1mrx 7y ago

What actually is a 4to6 gateway? For example, how would an IPv4 client connect to a 128-bit address like 2606:4700:20::6819:6c0d?

quintushoratius 7y ago
You contract with a tunnel broker (most, if not all, are free) to give you an address. If you have a lan then you can set up radvd (or similar) to distribute addresses. You may need to replace your router though. Your ipv6 packets head out over a 4to6 tunnel to your broker, and then out to the wider world.
- drdaeman 7y ago
  Nah, that's not the problem/solution, not in the ISP context. It's trivial for most ISPs (unless they have ton of ancient hardware and neglected to upgrade, or if they have very poor and limited peering options) to obtain an IPv6 block and set it up on their backbone network. All the complexity is about providing this to the end users. Depending on your tech stack, you may have no issues, or you may need to replace just about everything (NASes, accounting/billing system, etc - whatever pieces were built with IPv4-only in mind) Source: I worked for an ISP a while ago. We got our servers IPv6 connectivity, in, like, a day. We haven't solved IPv6 end-user connectivity (but it really wasn't a priority then), although was we had a few experimental connections - with lots of duct tape and random end-user issues whenever something was misconfigured (e.g. at the time not every site's AAAA record was actually responding, despite the existence).
drdaeman 7y ago
I can imagine a weird contraption of a custom DNS server that tracks client requests, returns unique private IPv4 addresses and simultaneously tells to some NAT-PT engine that this source IPv4 address talking to that destination IPv4 address needs to be translated to that IPv6 address. I can imagine this to be extremely fragile and break whenever an IP address is looked up using any different manner than plain DNS (e.g. by having IP in API responses, or just using DoH). Yet, I can imagine someone's probably already working on this abomination.
- unilynx 7y ago
  Just return the same IP for everything and check the Host header or SNI name to know where to forward requests to It’ll work fine for web traffic.
jotm 7y ago
https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64 There's some other tools to facilitate that. FWIW, I tried playing with IPv6 on my home LAN. all IPv6 intranet, IPv4 on the ISP WAN, all ran fine on OpenWRT routers with a bit of configuration.

Symbiote 7y ago

See Google's statistics. Denmark has a low adoption rate in Europe, but that can change fairly quickly if a large ISP implemented IPv6. The world is at 26% adoption. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html