4 ms·

I'm curious if there are people here that have migrated their home network to IPv6 only, and if yes, what are the challenges encountered? I suspect the biggest

by lifty 7y ago

I'm curious if there are people here that have migrated their home network to IPv6 only, and if yes, what are the challenges encountered? I suspect the biggest problem is that there still are many websites that only have IPv4

icebraining 7y ago
If you have a beefy router, you can install Tayga[1] to do the translation from 6-to-4 for all client devices. Then you can use Google's DNS server or run your own, to translate IPv4 addresses in the replies into IPv6 equivalents. [1] http://www.litech.org/tayga/ http://www.litech.org/tayga/
gerdesj 7y ago
IPv6 only is a bit daft as yet because you'll need a 6 to 4 gateway of some sort to see much of the web/internets. For starters, this: $ dig news.ycombinator.com AAAA ... fails I have been running dual stack at home for around five years now with only a couple of wobbles that I can point at my ISP losing their IPv6 and not noticing for a while.
- Dagger2 7y ago
  $ ip -4 addr show | grep eth0 # nothing $ dig news.ycombinator.com AAAA +short 64:ff9b::d1d8:e6f0 $ wget -6 https://news.ycombinator.com -O /dev/null Resolving news.ycombinator.com (news.ycombinator.com)... 64:ff9b::d1d8:e6f0 Connecting to news.ycombinator.com (news.ycombinator.com)|64:ff9b::d1d8:e6f0|:443... connected. HTTP request sent, awaiting response... 200 OK [...] ‘/dev/null’ saved [34663] WFM!
  - zzzcpan 7y ago
    It's a translated with DNS64 ipv4 address into a NAT64 ipv6. They have 64:ff9b prefix.
    - Dagger2 7y ago
      Indeed it is, and it works fine. v4-only websites aren't a problem for running v6-only.
      - gerdesj 7y ago
        I am now at home and tried your experiment but I have IPv4 as well as IPv6. The wget forced to v6 does not work here. That's a bug somewhere. My eyes are no longer happy 8( ... 8) ... ahh, all OK now!
        Dagger2 7y ago
        I have a NAT64 translator handling the translation, plus a DNS64 server to point clients to it. You probably don't have those, because it's typically easier to run native v4 instead. I just wanted to make the point that v4-only websites are totally not a problem.
        cesarb 7y ago
        > I just wanted to make the point that v4-only websites are totally not a problem. They will be once DoH breaks DNS64, unless Cloudflare invents a way to make it somehow work (perhaps hosting their own NAT64 gateway?).
        Dagger2 7y ago
        Since they seem to want to take over the internet, I guess that would be right up their street. Clients can also synthesize the DNS64 records themselves locally, or use 464xlat.
zamadatix 7y ago
As others have said NAT64 is your friend. Other than that I never thought about it since the day I flipped, it's not really as big a change as people make it out to be. Literally like the difference between HTTP/1.1 and HTTP/2. Yeah not all sites use HTTP/2 yet but how often would you notice if you didn't go looking for it?

by lifty 7y ago

icebraining 7y ago

If you have a beefy router, you can install Tayga[1] to do the translation from 6-to-4 for all client devices. Then you can use Google's DNS server or run your own, to translate IPv4 addresses in the replies into IPv6 equivalents. [1] http://www.litech.org/tayga/ http://www.litech.org/tayga/

gerdesj 7y ago

IPv6 only is a bit daft as yet because you'll need a 6 to 4 gateway of some sort to see much of the web/internets. For starters, this: $ dig news.ycombinator.com AAAA ... fails I have been running dual stack at home for around five years now with only a couple of wobbles that I can point at my ISP losing their IPv6 and not noticing for a while.

Dagger2 7y ago
$ ip -4 addr show | grep eth0 # nothing $ dig news.ycombinator.com AAAA +short 64:ff9b::d1d8:e6f0 $ wget -6 https://news.ycombinator.com -O /dev/null Resolving news.ycombinator.com (news.ycombinator.com)... 64:ff9b::d1d8:e6f0 Connecting to news.ycombinator.com (news.ycombinator.com)|64:ff9b::d1d8:e6f0|:443... connected. HTTP request sent, awaiting response... 200 OK [...] ‘/dev/null’ saved [34663] WFM!
- zzzcpan 7y ago
  It's a translated with DNS64 ipv4 address into a NAT64 ipv6. They have 64:ff9b prefix.
  - Dagger2 7y ago
    Indeed it is, and it works fine. v4-only websites aren't a problem for running v6-only.
    - gerdesj 7y ago
      I am now at home and tried your experiment but I have IPv4 as well as IPv6. The wget forced to v6 does not work here. That's a bug somewhere. My eyes are no longer happy 8( ... 8) ... ahh, all OK now!
      - Dagger2 7y ago
        I have a NAT64 translator handling the translation, plus a DNS64 server to point clients to it. You probably don't have those, because it's typically easier to run native v4 instead. I just wanted to make the point that v4-only websites are totally not a problem.
        cesarb 7y ago
        > I just wanted to make the point that v4-only websites are totally not a problem. They will be once DoH breaks DNS64, unless Cloudflare invents a way to make it somehow work (perhaps hosting their own NAT64 gateway?).
        Dagger2 7y ago
        Since they seem to want to take over the internet, I guess that would be right up their street. Clients can also synthesize the DNS64 records themselves locally, or use 464xlat.

zamadatix 7y ago

As others have said NAT64 is your friend. Other than that I never thought about it since the day I flipped, it's not really as big a change as people make it out to be. Literally like the difference between HTTP/1.1 and HTTP/2. Yeah not all sites use HTTP/2 yet but how often would you notice if you didn't go looking for it?