wongabu

4 ms·

1. 1.▲
   by wongabu 6mo ago

   BGP is not for everyone: get an ASN, your own prefixes, and run BGP. Compare that to the simplicity of ipv4 NAT. Ipv6 NAT66 is fundamentally broken, see sibling comment.
2. 2.▲
   by wongabu 6mo ago

   Have you tried it? NAT66 implies using fd00::/8, which then gets deprioritized in all devices below ipv4, in accordance with RFC 3484. The end result: all devices revert to using ipv4 on dual stack lan. Ipv6 is fundamentally broken for
3. 3.▲
   by wongabu 6mo ago

   Ipv4 does NOT have this problem. The typical setup is always NAT for ipv4 lan, so external address can be changed with minimal disruption. All ipv4 apps that require hole punching assume they will need to "discover" the external a
4. 4.▲
   by wongabu 6mo ago

   That's one ugly hack, which assumes (1) WAN1 has static ipv6 (the typical SME has dynamic DHCPv6 address...) (2) all the devices will behave correctly when running on NPT on failover WAN2. Many devices do not know about NPT which is ba
5. 5.▲
   by wongabu 6mo ago

   There is no working solution to ipv6 dual WAN failover, 30 years later... A critical design flaw that was simply ignored by the designers despite being used in almost any SME network. inb4 no you can't have all lan devices have multipl