mwan3 and IPv6

[Simon Iremonger]

> I consider IPv6 support independent of mwan3 refactoring. It works in
> my setup.

Thankyou for your detailed consideration of the mwan* IPv6
situations.

I can also point out, "as-is" if you add 'mwan3' package on
current OpenWrt 24.10.x and do not add any mwan3 configuration,
IPv6 gets 'disabled'.

The 'default' should be that routing tables etc are not affected,
somehow or other, any of the new mwan* packages and NAT66 functions
shouldn't create a change/issue just by being 'installed' ...


> Issue 2: Which first IP? In the end, the first one reported by odhcp6c
> because netifd keeps that sorting and returns that when someone queries

Certainly, I can say, in UK; some ISPs have the property that the
router gets an actual IPv6-"wan" address, and some do not.
E.g. Zen provide a separate /64 linking-block and AAISP provide
something like 2001:8b0:1111:[something] /128 per wan-link.

However, linking OpenWrt to VodaFone, only getting /56 delegation
and NO separate IPv6 on the WAN; so clearly practice varies.  In
one circumstance, once, I got OpenWrt ddns-scripts IPv6 to manage
to pick up a "network" or "interface" address and get the /56 ::1
addy as the IP address for OpenWrt itself.

Currently the Vodafone link certainly only shows link local
inet6 fe80::407a:[..]:8c0e peer fe80::[..]ff:fe[..]/128 scope link nodad


In any case, one way or another you need sensible way of coping with
different scenarios for IPv6 wans and 'what is my address' .....

> Solution from the mwan3 side: better source IP selection. This is

Exactly :O

> the need to merge it. This implementation rewrites the prefix if it
> does not fit to the output interface and otherwise keeps the address

I like that idea.


Hope that helps!

--Simon