Sly Gryphon @sgryphon@qoto.org

Night time shot, after an entertaining dinner at #AsamiTeppanyaki

Staying at Q1, Surfer's Paradise.

Started running D&D Curse of Strahd recently. One of the players used popular culture for inspiration and then created a custom miniature to match. #dnd #curseofstrahd #ttrpg

Have an #ipv6 only site or homeserver that you want to make available to ipv4 clients - try a free CDN service like #cloudflare who will proxy it for you.

@aluaces I just tested Cloudflare free plan on one of my websites. The site only has an AAAA address, but Cloudflare proxies both A and AAAA for you.

@aluaces also, check your mobile provider, as some support IPv6 but may not enable it. e.g. Telstra, in Australia, has had IPv6 for a long time, but only recently been configuring for dual stack (and now some are single stack IPv6).

@aluaces to make an IPv6 site available to IPv4 you need someone with an IPv4 address to provide a proxy. e.g. my hosting provider, Mythic Beasts, provides that for all customers.

Some content delivery networks (CDNs) also provide IPv4 proxy services. Some CDNs have free tiers, try Cloudflare.

Otherwise you need to pay for a very cheap dual stack server (all it needs do is proxy).

If you don't want general availability, you could also try an IPv6 tunnel broker, that will run an tunnel (over IPv4) to your device, e.g. laptop, allowing it to access IPv6 only resources. Try Hurricane Electric.

Again note that if you are self hosting on IPv4 then you would also be using NAT to the private range. The difference is not NAT (both use it), but whether you have an IPv4 address to use with the NAT.

@aluaces IPv4 usually require NAT anyway.

At least with an IPv6 server there is only one NAT, compared to hosting provider NAT to 10.x range, then virtual machine NAT to 192.168 range, then container NAT to 172.16 range.

An IPv4 private 172.16 k8s pod is as unreachable by an IPv4 client as IPv6. Any solution with IPv4 (even without IPv6) needs NAT.

@aluaces to be more specific, you don't need to set up IPv4 on the IPv6 machine, or your internal network, hence simplifying as you only need one set of configuration, one firewall, etc. (compared to dual stack).

You do however need to have IPv4 access on some other (single) machine to act as an outgoing NAT64 / incoming proxy.

But this is largely the same for IPv4 as you only have private IPv4 addresses so for outgoing need to go through NAT44 and incoming needs to port forward/proxy.

The gateway needs a public IPv4 address in both cases, but the rest of the IPv4 world does not know (can not tell) if your internal network is an IPv4 private range or IPv6.

@freemo @General there are plenty of decent Christmas movies - Die Hard and Lethal Weapon are two that come to mind :-)

@aluaces about 30% of the Internet (>50% in some countries) has IPv6 now.

But yes, for the other 70% for outgoing you need something like NAT64 (but seeing as a lot of outgoing uses NAT44 anyway, not a big difference).

For incoming you need something like a CDN or reverse proxy gateway (an IPv6 hoster may provide this for free). I have some blog entries on the subject: https://sgryphon.gamertheory.net/2021/01/02/ipv6-only-hosting

In my case, it is for me to remote access my services, and I have IPv6 on my mobile provider as well, so I don't really care if other people don't have access (they wouldn't be able to log in anyway).

@freemo @General I watch The Hogfather pretty much every year.