I just got another Fibre line activated in my household to take full advantage of Dual WAN Capability of the Flint2.
However, it seems you are only able to have IPv6 on Ethernet WAN1. There is not option for the Secondary WAN.
I am running OpenWrt 21.02-SNAPSHOT latest firmware, this was present on the firmware before as I only updated it today after the new installation.
As you can see via the screenshots - there is a IPv6 tab on WAN1 and no such option on WAN2.
This is also causing oddly that when I am connected to WAN2 - as the primary connection, devices still attempt to use the IPv6 addresses from the WAN1 with about 50% packet loss, which in turn is causing issues.
EDIT: After further digging, it does look like devices are getting a v6 address from the 2nd WAN, but say I ping something from terminal, it will use WAN1 v6 addressing. I go to a site like test-ipv6.com it uses the v6 address from the 2nd WAN.
I assume that your Flint2 Multi-WAN mode is Failover, and the following troubleshooting will be performed in this mode.
In addition, the 2 WANs IPv6 address should both have public IP, that is starting with 2, when copying the results to the forum, please mark the public IP before sending it.
Neither of these issues are normal behavior, I have not reproduced them locally.
Please help us check on your router.
When WAN2 is the primary connection of Flint2, how do you determine whether the client/router goes to WAN1 or WAN2?
SSH to router:
ifconfig
ip -6 r
traceroute6 www.google.com
ip -6 nei show dev eth1
ip -6 nei show dev lan1
I have put the priority so that WAN2 is first and test this via a trace route on v4 on a Mac. I do a trace route on v6 and it will use the WAN1 v6 address.
Your Mac has two IPv6 global links and they are public IPv6 address. If an IPv6 request is initiated, it will not pass through the router, but will directly go to the operator gateway and forwarding. However, we do not know why the Mac's IPv6 request will go randomly or 1 for http(s) and 1 for ping. Do you have Windows system, please have a try to see if the behavior be the same?
The router and Mac ping6 are the same ipv6 export, it is normal behavior.
The router IPv6 routing table is normal, the br-lan ipv6 address is normal.