#NAT in #IPv6 ( https://packetpushers.net/podcasts/ipv6-buzz/ipb194-naval-gazing-at-nat-in-ipv6/ ). 🤔
Don't "bring back #IPv4 habits", but networks hit real constraints. 🤷‍♂️ If your internal v6 addressing is tied to an #ISP prefix, then multi-homing, provider changes, or failover get messy. Renumbering is painful and running #BGP everywhere is unrealistic for branch designs. In those cases, v6-to-v6 translation, #NPTv6 (prefix translation), can be a practical shim to keep a stable internal prefix and translate it to the provider prefix at the edge.

Ergebnis von ein wenig Sonntagsarbeit: "Unique Local IPv6 Unicast Addresses (ULAs) und IPv6-to-IPv6 Network Prefix Translation (NPTv6)"

https://grupp-web.de/cms/2024/03/10/unique-local-ipv6-unicast-addresses-ulas/ #IPv6 #NPTv6

and that advantage goes out the window with stateless one-to-one #NPTv6 so what's the advantage over stateful one-to-many #NAT66... considering YOU NEED A STATEFUL FIREWALL ANYWAY...

As I've talked about before, a problem with #ipv6 is that when your prefix changes, you have to update all your config. My prefix from xfinity changed and I had to manually update all my static DNS, firewall rules, wireguard configs.. The "correct" solution to this seems to be #NPTv6, but #Mikrotik doesn't support it. So it's tempting to just do #NAT 66 and have it work the same as #IPv4.