FS#524 - odhcpd: stateful+stateless sends M flag in RA for prefix that will not DHCPv6 #5573
Labels
Comments
|
dedeckeh: Have you observed DHCPv6 clients behave in such way or is this based on a RFC interpretation ? |
|
EricLuehrsen: Yes to both. I have assorted devices with each their various quirks. Windows 10 and Debian derivatives seem to be enhancing robustness to unusual in-spec or out-of-spec behavior. Manufacture controlled devices like smart tv, blu ray player, car smart info-nav, and such seem to be bare minimum main stream. My smart tv is the most noisy about sending dhcpv6 solicit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
EricLuehrsen:
The M-Flag should only be set in RA when DHCPv6 assignment will occur in that prefix. This is related to FS#402, but where FS#402 may be a matter of style to some, this one is a bug. odhcpd sends M-Flag in RA on both prefixes but only DHCPv6 on ULA. This can confuse some client software, they don't accept only the ULA, and they continue to spam the router with solicits trying to get GA and ULA together. Whether or not debate occurs on DHCPv6 being split in stateful+less mode, if it is split, then the RA need to respect it.
The text was updated successfully, but these errors were encountered: