←back to thread

296 points jmillikin | 3 comments | | HN request time: 1.374s | source
Show context
pumplekin ◴[] No.44411628[source]
If you ever need a quick hack to get v4 connectivity over a true v6 only setup, you can use a public DNS64+NAT64 Gateway. You can find a list at https://nat64.net/public-providers. So for most regular use, all you are doing is changing DNS servers.

This is the combo.

** 1. DNS64

Synthesis of AAAA DNS records for things that don't have them to a NAT64 box.

$ dig +short @2a00:1098:2c::1 AAAA github.com

2a01:4f8:c2c:123f:64:5:141a:9cd7

** 2. NAT64.

Will take this traffic thats been sent to it because of DNS64 and protocol translate + NAT it for you.

$ curl --resolve github.com:443:[2a01:4f8:c2c:123f:64:5:141a:9cd7] https://github.com/

<loads github>

replies(2): >>44413023 #>>44417771 #
1. rfv6723 ◴[] No.44413023[source]
Using Cloudflare WARP would be much faster.

And you can connect directly to ipv4 addr via WARP.

replies(1): >>44425066 #
2. WorldMaker ◴[] No.44425066[source]
WARP is a full VPN tunnel. The above poster was suggesting if someone wanted to avoid a VPN tunnel, DNS64+NAT64 is a nice "hack" that just uses DNS as the tool to reestablish IPv4 connectivity. (It's also how most mobile/cell traffic today reaches IPv4, via DNS64+NAT64 gateways.)
replies(1): >>44430017 #
3. rfv6723 ◴[] No.44430017[source]
I don't use WARP's VPN mode.

I run WARP in socks proxy mode, and using ipt2socks for redirecting traffic to socks proxy port.

https://github.com/zfl9/ipt2socks