5 ms·

Indeed, the transition to IPv6-only networks is a timely and important step, and this is an interesting approach. In my opinion, NAT64 in combination with DNS6

Indeed, the transition to IPv6-only networks is a timely and important step, and this is an interesting approach. In my opinion, NAT64 in combination with DNS64 presents the most practical solution for home networks. This approach can be fully implemented by consumer routers, eliminating the need for any changes to client devices. If router manufacturers were to make NAT64 with DNS64 a default feature or, at the very least, an easily selectable option, it would significantly advance our progress toward widespread adoption of IPv6-only networks.

csdvrx 3y ago
Not just routers: android phones since 4.3 and iOS 12 both include a CLAT implementation to do just that. clatd https://github.com/toreanderson/clatd/ https://github.com/toreanderson/clatd/ is a nice and practical CLAT implementation: it does not "require" dns64 but can use it for single stateful translation instead of double
- jeroenhd 3y ago
  Windows 10+ has a native 464XLAT implementation for use with cellular networks as well. Most of the pieces are in place already but not all clients operate the same way. I think there's stil some streamlining to be done before any ISP will bother implementing such technology into their routers.
  - csdvrx 3y ago
    Windows just nails it. Now that I'm spending most of my time on the desktop with Linux, I've tried to get the same results tere and move to IPv6 only: with clatd it's mostly been a smooth ride. One small issue: I think T-Mobile is giving /56 but for some reason the Qualcomm 5G card only gives /64 through wwan0. However, checking the IPv6 returned by qmi with `--wds-get-current-settings` returns a different one each time, so I think the embedded Linux inside the Qualcomm cards does SLAAC and the equivalent of net.ipv6.conf.wwan0.addr_gen_mode=3 to randomize the IID for EUI64
  - crest 3y ago
    Recentish macOS versions include 464XLAT as well, but it isn't enabled on WiFi and Ethernet (by default).
Spivak 3y ago
Then add NAT 46, 44, and 66 and give no shits about any nonsense that happens outside your network while supporting any device and allowing people to go ipv6 only at any time. If v6 people didn't hate nat with the white hot intensity of a thousand suns [1] we could have had a smooth ipv6 path with the only necessary change being on consumer routers. [1] https://lwn.net/Articles/451914/ https://lwn.net/Articles/451914/
- csdvrx 3y ago
  This is a link to a thesis. Can you recommend some implementations for linux and talk about your experience?

csdvrx 3y ago

Not just routers: android phones since 4.3 and iOS 12 both include a CLAT implementation to do just that. clatd https://github.com/toreanderson/clatd/ https://github.com/toreanderson/clatd/ is a nice and practical CLAT implementation: it does not "require" dns64 but can use it for single stateful translation instead of double

jeroenhd 3y ago
Windows 10+ has a native 464XLAT implementation for use with cellular networks as well. Most of the pieces are in place already but not all clients operate the same way. I think there's stil some streamlining to be done before any ISP will bother implementing such technology into their routers.
- csdvrx 3y ago
  Windows just nails it. Now that I'm spending most of my time on the desktop with Linux, I've tried to get the same results tere and move to IPv6 only: with clatd it's mostly been a smooth ride. One small issue: I think T-Mobile is giving /56 but for some reason the Qualcomm 5G card only gives /64 through wwan0. However, checking the IPv6 returned by qmi with `--wds-get-current-settings` returns a different one each time, so I think the embedded Linux inside the Qualcomm cards does SLAAC and the equivalent of net.ipv6.conf.wwan0.addr_gen_mode=3 to randomize the IID for EUI64
- crest 3y ago
  Recentish macOS versions include 464XLAT as well, but it isn't enabled on WiFi and Ethernet (by default).

Spivak 3y ago

Then add NAT 46, 44, and 66 and give no shits about any nonsense that happens outside your network while supporting any device and allowing people to go ipv6 only at any time. If v6 people didn't hate nat with the white hot intensity of a thousand suns [1] we could have had a smooth ipv6 path with the only necessary change being on consumer routers. [1] https://lwn.net/Articles/451914/ https://lwn.net/Articles/451914/

csdvrx 3y ago
This is a link to a thesis. Can you recommend some implementations for linux and talk about your experience?