[Dnsmasq-discuss] [PATCH] DHCPv6: Honor assigning IPv6 address based on MAC address

Oliver Freyermuth o.freyermuth at googlemail.com
Tue May 14 14:29:55 BST 2019


Am 11.05.19 um 19:42 schrieb Kevin Darbyshire-Bryant:
> 
> 
>> On 6 Apr 2019, at 12:01, Geert Stappers <stappers at stappers.nl> wrote:
>>
>> On Mon, Apr 01, 2019 at 01:02:20AM +0200, Pali Rohár wrote:
>>> On Tuesday 12 February 2019 13:41:43 Geert Stappers wrote:
>>>> On 06-02-2019 21:29, Pali Rohár wrote:
>>>>> On Friday 11 January 2019 17:52:43 Pali Rohár wrote:
>>>>>> On Monday 17 December 2018 18:41:09 Pali Rohár wrote:
>>>>>>> Currently IPv6 addresses are assigned to tuple (IAID, DUID). When system
>>>>>>> changes IAID/DUID then old assigned IPv6 address cannot be reused, even
>>>>>>> when in config file was DHCPv6 assignment based on MAC address (and not on
>>>>>>> DUID).
>>
>>   ...
>>
>>>>>> Hello, can somebody look at this patch?
>>>>>>
>>>>>> I remember that more people asked for ability to assign IPv6 address
>>>>>> based on MAC address specified in config file, rather then IAID/DUID.
>>>>>>
>>>>> PING
>>>>>
>>>> Another request for
>>>>
>>>> Hey, could this patch get reviewed?
>>>>
>>>>
>>> Hello, can somebody review this patch?
>>>
>>
>> FWIW
>>
>> * The (four months old) patch does get applied cleanly.
>> * My compiler is happy with it
>> * Executable remains running upon start ( no early crash )
>> * I'm unable to test the (new) IPv6 functionality
>>
>>
>> Where in the "patch pipeline" is Pali's patch?
>>
>>
>> Regards
>> Geert Stappers
> 
> I’ve been using this patch to tame qnap’s frustrating dhcpv6 assignment limitations for many months.  It’s immensely useful.

Same here. In an automated deployment situation, client changes DUID in each phase: 
- PXE (if done via IPv6)
- Installation time (from ramdisk)
- Final OS after installation
This may improve if newer versions of dhcpcd get packaged in installer ramdisks and OS, and also for systemd-dhcp,
but I am still unaware of any implementation of machine-id as base for the client DUID in dhclient and of course the implementations are all not exactly the same. 
And then there is still the UEFI doing the PXE part, systems with broken machine-id etc.... And of course, dual booting if not set up with identical cliend-DUID. 

In general, my belief is that the RFC was made without real life use cases in mind and hence did not think of these. 
The patch is very helpful to overcome these issues and matches user expectation (when specifying a MAC address in the config file, I want it to be used). 

Cheers,
	Oliver

> 
> 
> Cheers,
> 
> Kevin D-B
> 
> gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 



More information about the Dnsmasq-discuss mailing list