Re: [Dnsmasq-discuss] DHCPv6 solicit ignored by dnsmasq after UEFI -> iPXE -> Deploy ramdisk

[Geert Stappers]

On Thu, Nov 21, 2019 at 07:16:40PM +0100, Harald Jensås wrote:
> On Tue, 2019-11-12 at 16:56 +0100, Harald Jensås wrote:
> > When using DHCP-stateful addressing, radvd config below, UEFI
> > succesfully request/advertize 2x IP's and downloads the bootimage
> > (iPXE). UEFI (OVMF) then releases the addresses and iPXE then boots.
> > 
> > iPXE does one request/advertize and dowloads and boot the deploy
> > ramdisk (CentoOS 7). dhclient in CentOS 7 starts logging: "XMT:
> > Solicit
> > on eth0, interval ...", dnsmasq ignores the DHCPv6 Solicit messages?
> > I
> > don't understand why it's ignored? (Config files, and annotated
> > traffic
> > dump + dnsmasq logs below.)
> > 
> 
> This turned out to be an issue with nic device model's used on virtual
> machines in my lab. Using virtio instead of e1000 solved the problem.
 
Thanks for reporting that.

> Sorry about the noise.

I wish more people report back on the issue they reported.


Groeten
Geert Stappers
-- 
Leven en laten leven

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

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

[Harald Jensås]

Bumping this patch again: 
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2018q4/012707.html

I see there have been several request to include this on the list:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q1/012895.html 
(and others ...) afaict there has not been any objections to the
patch.


We are trying to make Openstack Ironic deploy baremetal servers in a
setup where Openstack Neutron is used. Neutron uses dnsmasq and the MAC
address as identifier to assign IPv6 addresses in a static only setup,
config details at bottom of this mail.

The problem with DUID/IAID changes as the baremetal node is moving
trough the deployment phases UEFI->iPXE->Deploy Ramdisk resulting in
"no address available" has always been a blocker for this to work. (The
issue was discussed on this list a some time ago, 
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/thread.html#11267
)

This patch solves this problem of changing DUID/IAID's.

 Is there a reason not to merge the patch?



/usr/sbin/dnsmasq \
 -k \
 --no-hosts \
 --no-resolv \
 --pid-file=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-
52e1ecb11e65/pid \
 --dhcp-hostsfile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-
52e1ecb11e65/host \
 --addn-hosts=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-
52e1ecb11e65/addn_hosts \
 --dhcp-optsfile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-
52e1ecb11e65/opts \
 --dhcp-leasefile=/var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-
52e1ecb11e65/leases \
 --dhcp-match=set:ipxe,175 \
 --dhcp-userclass=set:ipxe6,iPXE \
 --local-service \
 --bind-dynamic \
 --dhcp-range=set:subnet-2b009f45-e0e2-4888-bb19-
8d46e51717b8,fd12:3456:789a:1::,static,64,86400s \
 --dhcp-option-force=option:mtu,1450 \
 --dhcp-lease-max=16777216 \
 --conf-file= \
 --domain=localdomain

$ cat /var/lib/neutron/dhcp/6c9c3845-a101-47fa-a491-52e1ecb11e65/host
fa:16:3e:8b:07:9f,host-fd12-3456-789a-1
--4.localdomain,[fd12:3456:789a:1::4]
fa:16:3e:9f:b7:e3,host-fd12-3456-789a-1
--ed.localdomain,[fd12:3456:789a:1::ed]



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