Post #1183485
2026-04-14 09:59 UTC
@Baa Configuring IPv6 on a router:
- set up firewall rules
- add IP addresses to interfaces
- done™
Configuring IPv4:
- set up firewall rules
- set up NAT and a bunch of port forwards because you only have one v4 (if you're lucky and not behind CGNAT)
- oh shit now you can't communicate with your server over the public IP, time to also set up hairpin NAT!
- wanna add a new device accessible over the internet? oh you better start remembering what ports everything is on, or just give up and set up a VPN to access everything, assuming it doesn't need to be exposed
The worst thing about IPv6 is still having to set up IPv4 alongside it, I really want v4 to die
Replies (1)
-
@lispi314@udongein.xyz 2026-04-14 16:43
@awooo@floofy.tech @Baa@mk.absturztau.be oh shit now you can't communicate with your server over the public IP, time to also set up hairpin NAT! I mostly used internal DNS for everything already, so I instead just added split-horizon configuration with views to unbound (ref). The clients just use the same names and everything just transparently works because the DNS replies differently based on where the connection is coming from.