New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#2019 - odhcpd IPv6 RA Flags #7160
Comments
artturnip: My apologies for the poor formatting and typos in this: The last paragraph should read: Therefore the M flag should be able to be set whilst the internal DHCPv6 server is |
dedeckeh: This behavior is in place since an issue was logged no M/O flags must be set if the DHCPv6 server is not enabled; see https://bugs.openwrt.org/index.php?do=details&task_id=1457 |
artturnip: Surely that previous example is just a misconfiguration? The user has deliberately told odhcpd to advertise DHCPv6 as available by setting Note that this is exactly the functionality I am trying to replicate! |
artturnip: If the user did not want DHCPv6 to be advertised by the router then they should have set |
dedeckeh: Experience has learned me very few devices respect the M/O flags in the RAs and still start DHCPv6 even if the M/O flags are not set. So using the M/O flags to disable DHCPv6 is not an option in the real world |
artturnip: Even so, should we not try to adhere to IETF standards wherever possible? The intent behind the O and M flags is to indicate to the client that a DHCPv6 server is available //somewhere// on the network -- it need not be on the router. A misconfiguration reported as an issue should not lead OpenWrt to disregard the IETF standards. Even if other devices don't adhere to the standards, this should not be a reason as to why we should not. |
artturnip:
Supply the following if possible:
This problem occurs on the TP-Link TL-WDR3600 v1 with OpenWrt 18.06.1
Steps to reproduce:
Configure /etc/config/dhcp as follows:
[...]
config dhcp 'lan'
option interface 'lan'
option ra 'server'
option ignore '1'
option ra_management '2'
option dhcpv6 'disabled'
[...]
Expected behaviour: Router gives out RAs with M and O flags set and A flag not set.
Actual behaviour: RAs do not have any of the three flags set
The M flag only indicates that a DHCPv6 server is //available// but it does not necessarily have to be at the same address as the router. Therefore the M flag should be able to be set whilst the internal DHCPv6 server is enabled.
The text was updated successfully, but these errors were encountered: