Dear dnsmasqers,

I fear the following is a design issue of DHCPv6, but I wonder if there's a way 
to overcome it with dnsmasq... 

When automatically deploying machines via PXE / network installer, there's 
usually first a DHCPv6 client running in the installer,
and afterwards (when the machine is installed) the "real" DHCPv6 client running 
on the machine. 
Naturally, both will usually have different client DUIDs... 

Using dnsmasq's functionality to perform DHCPv6 address assignment based on MAC 
this works fine for the first client, but the second DHCPv6 client will not get 
an address until the old lease is expired. 

In general, I feel this is the correct behaviour, but it's of course rather 
inconvenient when deploying machines automatically - 
they will retrieve an IPv6 address with the network installer, and then not get 
one after the first reboot. 
Also, when reinstalling them, they will not get an address in the installer if 
the lease from their "old life" is still valid. 

Does somebody have a good solution for this? 
Is there something like "id:*" for IPv4 implemented for the IPv6 world (i.e. 
something like "duid:*")? 

Cheers and all the best,

Dnsmasq-discuss mailing list

Reply via email to