Jim Pingle wrote in #note-3:
There still isn't enough valid information in that thread to suggest a bug, and LLM output cannot be trusted.
As I stated in the forum thread, the LLM wasn’t trusted. It was information that provided an explanation where none existed, and there were no replies which provided an alternative explanation. The behavior I experienced was consistent with it. So barring any other suggested explanation, it wasn’t worth discarding.
I have a setup here in my lab with two separate IPv6 WANs, with one or more LANs tracking each WAN, and IPv6 addresses handed out from Kea, and it all works. Configurations for both WANs are present where expected.
That’s good to hear. But you didn’t necessarily follow my path to get there, so it may be that your existing configuration (without being changed, or with some existing configuration that prevents the issue from happening) keeps you from experiencing the problem. I mentioned this possibility in the forum thread. That your configuration is working doesn’t eliminate the possibility of a bug affecting mine.
Odds are much higher there is some problem in your configuration or environment than a bug in the software, and figuring that out is a process that belongs on the forum.
I may indeed have a problem in configuration, but as I did a factory reset twice and ended up in the same place with the same problem, I imagine there’s a decent possibility there is a bug. Distilled to its most granular explanation — IPv6 interface configuration changes made in the UI console never make it to dhcp6c.config file for the second WAN interface. Perhaps there are other config issues on my end (not sure what b/c I was using vanilla config off factory reset), but unless config changes made in the UI console not taking under the hood though remaining persistent in the UI is considered normal behavior, I imagine there’s a pfSense bug involved.
As for the forum, my original post was 2 weeks ago, unfortunately didn’t produce any help, save to advise I submit the issue here. If I have reached the end of the road getting help, I suppose until something changes, pfSense is a single-WAN-only path for me.
Updated by 
Updated by