Comment 1 for bug 2011687

Hi,

Thanks for the bug.

So I think the code is operating properly based on my reading of the IPv6 RFC.

https://www.rfc-editor.org/rfc/rfc4861#section-4.2

    If the M flag is set, the O flag is redundant and
    can be ignored because DHCPv6 will return all
    available configuration information

I guess we can do one of two things:

1) Change the docs to say we don't need to set O=1 based on the RFC.

2) Change the code to set it anyways, but still document it's unnecessary.

I would have to look at what radvd does in the second case since we don't want to cause any issues, either by having it complain or worse.