[systemd-devel] [PATCH 00/24] Initial DHCPv6 client support

[Tom Gundersen]

On Fri, Jun 13, 2014 at 6:26 PM, Dan Williams <dcbw at redhat.com> wrote:
> On Fri, 2014-06-13 at 16:44 +0300, Patrik Flykt wrote:
>>       Hi,
>>
>> This patch set provides initial DHCPv6 client support for
>> systemd-networkd. It adds support for ICMPv6 Router Solicitation sending
>> and Router Advertisment receiving and the very basic Solicit, Advertise,
>> Request and Reply message transactions. Networkd is able to start DHCPv6
>> negotiation for a link, but doesn't yet do anything with the result.
>>
>> As only the initial DHCPv6 client side support is implemented, this patch
>> set omits the following features specified in RFC 3315:
>>  - Rapid Commit in the Solicit message
>>  - Information Request, should the router only announce the availability
>>    of "Other" information
>>  - Reacquiring of an address, i.e. Renew, Rebind, etc.
>>  - Temporary adresses, option requesting, elapsed time options
>>  - DHCPv6 authentication
>>
>> ...and a few more that I for sure have forgotten from this list. The
>> intent is to have the remaining parts essential for the protocol
>> functionality to be done as quickly as possible after this patch set.
>>
>> On startup, the DHCPv6 client implementation sends Router Soliciations
>> in order to receive Router Advertisments. Only the Managed/Other flags
>> in the Router Advertisment are currently used, any prefix information
>> is currently ignored. ICMPv6 and a basic test case is handled by patches
>> 02-04 with the basic DHCPv6 library and test case provided in patches 01
>> and 08.
>
> For future consumers of the library, can the RA/RS behavior be
> selectively disabled?

No objections from me, but out of interest, what is your desired
behaviour here? Will this option be exposed to the user, or do you
have some other way to determine whether or not to do RA/RS, or do you
simply do it in a different way?

Cheers,

Tom