Yes, it is a fringe case, becoming noticeable only through a convergence of particular circumstances. It has had no detrimental effect on my Linux clients, which politely disregard the unusable DNS IPv6 address. Only Android feels a need to hold a grudge, refusing to send its queries to the working IPv4 DNS address.
For now, I believe the soundest and least intrusive workaround is to submit the value directly through the call to UCI.
Meanwhile, feel free to offer any specific information that would be helpful to include in an issue report.
Nevermind, does not sound like a bug to me. The screenshot above indicates that just DHCPv4 has been disabled. To inhibit DHCPv6 on an iface you need to toggle these options:
Sorry, I had meant to file a report on the tracker, but never had a chance.
When the network interface is set to be a DHCP client, all the options for disabling (or enabling) the DHCP server, whether for IPv4 or IPv6, are removed from the graphical web interlace. It is impossible to disable the server explicitly through the web interface. This change suggests that the server is implicitly disabled, and most users, understanding such a constraint as sensible, would not seek further to disable the DHCP server (even if options were visible in the graphical interface) on an interface already set as a DHCP client.
The screen capture above is not representative of the circumstances I encountered. It was an attempt by another user to show me how to try to resolve the issue.
My build is versioned 21.02-SNAPSHOT r15949-b2c9a8741f.
What is the description of the fix you are referencing?
The following, taken from the commit message, does not seem to capture the problem encountered in this discussion:
Prevent enabling ra/dhcpv6 server mode on non-static or master interfaces
Such describes how the system appears to behave from the behavior of the graphical interface, bu the actual operation of the networking components does not match.
