Skip to content
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

radvd.conf.5.man is wrong about M/O flags documented in RFC 4862 #232

Open
Zocker1999NET opened this issue Sep 6, 2024 · 0 comments
Open

Comments

@Zocker1999NET
Copy link

to quote from the man page:

radvd/radvd.conf.5.man

Lines 272 to 289 in f2de476

.TP
.BR AdvManagedFlag " " on | off
When set, hosts use the administered (stateful) protocol for address
autoconfiguration in addition to any addresses autoconfigured using
stateless address autoconfiguration. The use of this flag is
described in RFC 4862.
Default: off
.TP
.BR AdvOtherConfigFlag " " on | off
When set, hosts use the administered (stateful) protocol for
autoconfiguration of other (non-address) information. The use of
this flag is described in RFC 4862.
Default: off

The man page states that the Managed & OtherInformation flags are documented in RFC 4862. However, this does not seem the case. Quoted from RFC 4862, Appendix C:

  • Removed the text regarding the M and O flags, considering the maturity of implementations and operational experiences. ManagedFlag and OtherConfigFlag were removed accordingly. (Note that this change does not mean the use of these flags is deprecated.)

I do not have a better source for information yet, as I’m trying myself to find out which of these flags is supposed to be set when having DHCPv6 in prefix delegation mode only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant