4 ms·
That's wrong. Note the last bullet from the /why page: > The primary purpose of this service is to encourage deployment of IPv6. The primary method this servic
by dundarious 5y ago
That's wrong. Note the last bullet from the /why page:
> The primary purpose of this service is to encourage deployment of IPv6. The primary method this service uses to encouraging deployment of IPv6 is to lend a helping hand to two groups of users.
> * Users of IPv6-only networks who need NAT64 in order to reach legacy services.
> * Users who due to no fault of their own is stuck on an IPv4-only network behind NAT.
- wmf 5y agoAll the instructions require IPv6 so ¯\_(ツ)_/¯
- dundarious 5y agoYou know what, on second thought, I think you're totally right and I'm totally wrong. I had this marked down as something to help me out because I only have 6to4 from my ISP, and I often get at least one relay that's broken. But NAT64 _is_ primarily for v6 access to v4. As far as I can see, running a v4 node just adds another endpoint to the network for those v6 people to use.
- progval 5y agoNot these ones: https://p2p.nat64.dk/v4peer https://p2p.nat64.dk/v4peer And also, https://p2p.nat64.dk/why https://p2p.nat64.dk/why mentions: "IPv4-only users contribute by providing a communication path to IPv4-only services. In return they get external reachability of their host by having an RFC 1918 address which can be reached through NAT64. That means the IPv4-only peer is now reachable through a static IPv6 address even though it started out having only IPv4 access tyhrough NAT. "
- dundarious 5y agoWould be great to have an explanation of how that works. Where is that v6ified rfc1918 address specified? Does that mean a v6 host running v6peer can just ping that rfc1918 address and get to the v4peer behind a NAT?