Re: [Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[P W]

On Fri, May 25, 2018 at 03:34:08PM +0200, Oliver Freyermuth wrote:
> Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
> >> On 25 May 2018, at 13:07, Oliver Freyermuth wrote:
> >>
> >> 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...
> > 
> > 
> > Hi Oliver,
> > 
> > I???ve a similar/same problem when rebooting some QNAP NAS boxen,
> > first boot/introduction to dnsmasq and they get both IPv4 & v6
> > addresses set to fixed values based on MAC address.  On reboot whilst
> > IPv4 is fine, IPv6 is not reallocated to the original address but
> > rather a new one.  By curious co-incidence I just started looking
> > into this problem today though it has been bugging me for months :-)
> > Have tried various combinations of MAC address & DUID.
> > 
> 
> Dear Kevin, 
> 
> I think it's exactly the same issue. 
> Comparing:
> > Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
> > DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba
> with
> > Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
> > DHCPSOLICIT(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
> it seems the QNAP NAS box is using a fresh client DUID each reboot... 


Patches Welcome

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[Oliver Freyermuth]

Am 25.05.2018 um 15:30 schrieb Kevin Darbyshire-Bryant:
> 
> 
>> On 25 May 2018, at 13:07, Oliver Freyermuth  
>> wrote:
>>
>> 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...
> 
> 
> Hi Oliver,
> 
> I’ve a similar/same problem when rebooting some QNAP NAS boxen, first 
> boot/introduction to dnsmasq and they get both IPv4 & v6 addresses set to 
> fixed values based on MAC address.  On reboot whilst IPv4 is fine, IPv6 is 
> not reallocated to the original address but rather a new one.  By curious 
> co-incidence I just started looking into this problem today though it has 
> been bugging me for months :-)  Have tried various combinations of MAC 
> address & DUID.
> 
> Without meaning to thread hijack!  If it’s not effectively the same issue 
> will gladly start a new thread.

Dear Kevin, 

I think it's exactly the same issue. 
Comparing:
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
> DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba
with
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
> DHCPSOLICIT(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
it seems the QNAP NAS box is using a fresh client DUID each reboot... 

Cheers,
Oliver

> 
> 
> First boot with fresh dnsmasq
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 client MAC 
> address: 24:5e:be:0c:bc:ba
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
> DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
> DHCPREPLY(br-lan) 2a02:c7f:beef:2000::e 
> 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba Statler
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 tags: lan, 
> known, dhcpv6, br-lan
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 
> 14 option:  2 server-id  00:01:00:01:21:92:2f:dc:60:e3:27:af:9e:51
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 
> 40 option:  3 ia-na  IAID=3132886206 T1=21600 T2=37800
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 nest size: 
> 24 option:  5 iaaddr  2a02:c7f:beef:2000::e PL=43200 VL=43200
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size:  
> 9 option: 13 status  0 success
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size:  
> 1 option:  7 preference  255
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 
> 29 option: 24 domain-search  lan.darbyshire-bryant.me.uk
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 
> 16 option: 23 dns-server  2a02:c7f:beef:2000::da2b:da2b
> Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 
> 38 option: 39 FQDN  Statler.lan.darbyshire-bryant.me.uk
> 
> 
> And now a reboot of the client:
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 available 
> DHCP range: 2a02:c7f:beef:2000::1000 -- 2a02:c7f:beef:2000::
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 client MAC 
> address: 24:5e:be:0c:bc:ba
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
> DHCPSOLICIT(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
> DHCPADVERTISE(br-lan) 2a02:c7f:beef:2000::9c72 
> 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba Statler
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 tags: lan, 
> known, dhcpv6, br-lan
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
> 14 option:  1 client-id  00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
> 14 option:  2 server-id  00:01:00:01:21:92:2f:dc:60:e3:27:af:9e:51
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
> 40 option:  3 ia-na  IAID=3132886206 T1=21600 T2=37800
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 nest size: 
> 24 option:  5 iaaddr  2a02:c7f:beef:2000::9c72 PL=43200 VL=43200
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
>  9 option: 13 status  0 success
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
>  1 option:  7 preference  255
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
> 29 option: 24 domain-search  lan.darbyshire-bryant.me.uk
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
> 16 option: 23 dns-server  2a02:c7f:beef:2000::da2b:da2b
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
>  9 option: 39 FQDN  Statler
> Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 available 
> DHCP range: 2a02:c7f:beef:2000::1000 -- 

Re: [Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[Kevin Darbyshire-Bryant]

> On 25 May 2018, at 13:07, Oliver Freyermuth  
> wrote:
> 
> 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...


Hi Oliver,

I’ve a similar/same problem when rebooting some QNAP NAS boxen, first 
boot/introduction to dnsmasq and they get both IPv4 & v6 addresses set to fixed 
values based on MAC address.  On reboot whilst IPv4 is fine, IPv6 is not 
reallocated to the original address but rather a new one.  By curious 
co-incidence I just started looking into this problem today though it has been 
bugging me for months :-)  Have tried various combinations of MAC address & 
DUID.

Without meaning to thread hijack!  If it’s not effectively the same issue will 
gladly start a new thread.


First boot with fresh dnsmasq
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 client MAC 
address: 24:5e:be:0c:bc:ba
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 
DHCPREPLY(br-lan) 2a02:c7f:beef:2000::e 
00:01:00:01:22:9a:b4:43:24:5e:be:0c:bc:ba Statler
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 tags: lan, 
known, dhcpv6, br-lan
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 14 
option:  2 server-id  00:01:00:01:21:92:2f:dc:60:e3:27:af:9e:51
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 40 
option:  3 ia-na  IAID=3132886206 T1=21600 T2=37800
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 nest size: 24 
option:  5 iaaddr  2a02:c7f:beef:2000::e PL=43200 VL=43200
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size:  9 
option: 13 status  0 success
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size:  1 
option:  7 preference  255
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 29 
option: 24 domain-search  lan.darbyshire-bryant.me.uk
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 16 
option: 23 dns-server  2a02:c7f:beef:2000::da2b:da2b
Fri May 25 12:47:13 2018 daemon.info dnsmasq-dhcp[26168]: 5514926 sent size: 38 
option: 39 FQDN  Statler.lan.darbyshire-bryant.me.uk


And now a reboot of the client:
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 available 
DHCP range: 2a02:c7f:beef:2000::1000 -- 2a02:c7f:beef:2000::
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 client MAC 
address: 24:5e:be:0c:bc:ba
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
DHCPSOLICIT(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 
DHCPADVERTISE(br-lan) 2a02:c7f:beef:2000::9c72 
00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba Statler
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 tags: lan, 
known, dhcpv6, br-lan
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
14 option:  1 client-id  00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
14 option:  2 server-id  00:01:00:01:21:92:2f:dc:60:e3:27:af:9e:51
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
40 option:  3 ia-na  IAID=3132886206 T1=21600 T2=37800
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 nest size: 
24 option:  5 iaaddr  2a02:c7f:beef:2000::9c72 PL=43200 VL=43200
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size:  
9 option: 13 status  0 success
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size:  
1 option:  7 preference  255
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
29 option: 24 domain-search  lan.darbyshire-bryant.me.uk
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size: 
16 option: 23 dns-server  2a02:c7f:beef:2000::da2b:da2b
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 12603117 sent size:  
9 option: 39 FQDN  Statler
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 available 
DHCP range: 2a02:c7f:beef:2000::1000 -- 2a02:c7f:beef:2000::
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 client MAC 
address: 24:5e:be:0c:bc:ba
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 
DHCPREQUEST(br-lan) 00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 
DHCPREPLY(br-lan) 2a02:c7f:beef:2000::9c72 
00:01:00:01:22:9a:b7:2b:24:5e:be:0c:bc:ba Statler
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 tags: lan, 
known, dhcpv6, br-lan
Fri May 25 12:59:40 2018 daemon.info dnsmasq-dhcp[26168]: 15821508 sent size: 
14 option:  1 client-id  

Re: [Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[Pali Rohár]

On Friday 25 May 2018 14:07:34 Oliver Freyermuth wrote:
> 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 address,
> 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,
>   Oliver

Hi Oliver!

dnsmasq for DHCPv6 stores in lease file IAID, not DUID. But assignment
of address is done either by DUID or MAC address.

I think you hit some problem affected by the way how is IPv6 address
assigned according to DUID, IAID, MAC address and status of lease file.

2 years ago I tried to discuss with Simon about possibility to assign
one address to more DHCP requests identified by MAC address and one of
needed thing was probably extension of lease file (to include also MAC
address and DUID) and handling of requests which already have address
assigned in lease file. Apparently until now Simon has not response
about it and I gave up trying to ping him again...

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q1/010404.html

-- 
Pali Rohár
pali.ro...@gmail.com

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

[Dnsmasq-discuss] DHCPv6 with dnsmasq for automated deployments

[Oliver Freyermuth]

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 
address,
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,
Oliver

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss