Am Thu, Feb 12, 2026 at 01:58:36PM +0000, schrieb Simon Iremonger: > On 17/11/2025 19:33, Jonas Lochmann wrote: > > I consider IPv6 support independent of mwan3 refactoring. It works in > > Regarding the IPv6 tracking, there is the issue with the source IP > > selection. > > Without knowing ddns-scripts, they could be affected by the same issues. > > When asking a web service, then the kernel just picks the source IP > > and usually does a good job when doing that. > > I can say that -- ddns-scripts in 25.12-SNAPSHOT r32607 (with a recent > fix included already) now works fine for IPv6 address detection on > interface, network, and URL using checkipv6.dyndns.com etc... > It obviously has been improved since 24.10.5 where many of these did > not work.
I disagree regarding the mode "network". It uses network_get_ipaddr6 which is unstable - if it returns your public IP after boot, it can stop doing that after the first address change because odhcp6c always puts new IPs at the end of the list, netifd keeps it like that and the helper function returns the first IP. This is solved in my OpenWrt fork. Patches were submitted, but not reviewed or accepted yet. And the patches are not new. That's why I started my fork. > HOWEVER; I basically am interested, what is the state of affairs of > using mwan3 in 25.12.0 OpenWrt ? [Seems to be "mwan3-2.12.0-r3"] > > Issues expected, incompatible with current fw4 etc? > Anything that can be pulled/fixed for upcoming release? No issues with fw4. Depending on your needs, you could miss certain features in fw4 that are helpful in combination with mwan3. The issue with network_get_ipaddr6 returning the wrong address could occur. > If this needs some testing I may be able to help. I could > certainly see if IPv6-tracking works where it didn't before. IPv6 tracking is the simple part and already worked when I started using mwan3. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
