3 ms·
Easy - it sucks! I tried to failover wan on a biz network. With ipv4 NAT this just works. Local traffic doesn’t even blip. IPv6 is comically bad here. All the
by onphonenow 4y ago
Easy - it sucks!
I tried to failover wan on a biz network. With ipv4 NAT this just works. Local traffic doesn’t even blip. IPv6 is comically bad here. All the autoconfig magic falls on its face. I don’t want rotating ipv6 addresses everywhere. Things like nptv6 as a workaround badly supported. NAT66 etc results in comically large internal address space - the list goes on. Can we do ipv5? Ohh, and my isps won’t give out static ipv6 blocks to save address space but a static ipv4 block is easy.
- icod1 4y agoyou can disable privacy extensions if you don't want "rotating ipv6 addresses everywhere"
- icedchai 4y agoIn a fail over situation, such as a small biz scenario with multiple providers, but no BGP, you'll have to deal with rotating prefixes. One alternative would be to NAT to the other provider prefix's during fail over (actually NPt: network prefix translation.) Depending on your firewall / router this may be easier said than done.
- onphonenow 4y agoRight. NPT is not well supported. NAT66 is out there, but when you think of address space size is totally ridiculous. That said it does solve a bunch of issues.