Honestly, the decoupling of Wifi, IPv4 and IPv6 address configuration in Linux, OpenWRT, and FreeBSD is really a mistake, and it's gotta stop. It's a bug, not a feature.
I left out OSX, Android, IOS and Windows from your list on purpose.
My understanding is that OSX and IOS actually already do extensive coupling
of layer-2 and layer-3 configurations, such that one can actually do things
like recognize that the the layer-3 network configuration(s) on a particular
ESSID is broken, and pick another ESSID.
I know that there are interactions between IPv4 and IPv6 configurations on
Windows *ALREADY*, but I can't give you the details.
As for Android, as someone who has been deep into the code, there is so
little IPv6 code in there at all, there isn't really anything to replace.
There are multiple ways to couple things sensibly.
On OpenWRT, dnsmasq is pretty much doing it all already.
On Linux desktops, dbus and NetworkManager is there. Many don't like NM, but
it's getting better.
So that leaves FreeBSD.
Remember: you don't have to implement this. Where it matters most is on home
routers; where failing to turn off IPv4/recognize there-is-none, results in
being on an IPv4 NOTwork.
{I didn't buy the argument that people doing IPv6 didn't want to run IPv4
DHCP, at first, but slowly I've gotten to understand the numerous layer-2 and
layer-3 savings by not having to have the whole DHCPv4 relay and broadcast
processing occuring. DHCPv4 is not a young protocol...}
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
pgpjp9dOWMARh.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
