Re: Re: DHCPv6 Rapid Commit
Roy Marples
Sun Jan 31 13:48:20 2016
On 2016-01-31 12:37, Nick Williams wrote:
I found a reference to rapid commit in the man page for dhcpcd [1]
(but not the man page for dhcpcd.conf):
--test: … “The rapid_commit option is not sent in TEST mode so
that the server does not lease an address.”
So, given that this is the only mention in any of the documentation, I
gather that:
- dhcpcd supports rapid commit
Yes
- Rapid commit is always enabled except in test mode
- Other than test mode, there is no switch or configuration option
for disabling rapid commit
No, it's explicitly enabled in the default dhcpcd.conf. Here is the
text:
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option
set
# on the server to actually work.
option rapid_commit
Also, I don't document all DHCP{4,6} options in my man pages.
See here for supported options:
$ dhcpcd -V | grep rapid
080 rapid_commit flag norequest
00014 rapid_commit flag norequest
Or you can look at the file dhcpcd-definitions.conf in the dhcpcd source
tree to find the full definitions and decoding for every RFC DHCP option
I know of, along with a short description and RFC number.
On Jan 29, 2016, at 9:15 PM, Nicholas Williams
<nicholas+vyos@xxxxxxxxxxxxxxxxxxxx> wrote:
Does dhcpcd have any support for DHCPv6 Rapid Commit [1]? I looked
through the config and didn't find any mention of it. I thought
maybe it could be configured with a dhcp6_option configuration
option, but then it occurred to me that dhcpcd would probably have
to be actively involved in Rapid Commit, so there would probably be
an actual config option for it.
If it's not an existing feature, should I just file an enhancement
request here [2]?
Nick
[1]
http://www.techtutorials.net/articles/ipv6_training_cisco_what_is_dhcp_for_ipv6_rapid_commit_.html
[1]
[2] http://roy.marples.name/projects/dhcpcd/ticket [2]
I must have missed that email ..... but yes, that's the right place it
file tickets and feature requests.
However, it's normally better to discuss both on the mailing list before
filing one, because fossil-scm doesn't have any email support and you
need to track the ticket changes by a RSS news feed.
Roy
Archive administrator: postmaster@marples.name