Hi
On Wed, Jul 28, 2021 at 05:22:43PM +0200, Thomas Goirand wrote:
> - Initial boot:
> 2021-07-28T12:26:38.804683+00:00 pub1-network-3 dnsmasq-dhcp[3765807]:
> DHCPSOLICIT(tap67fa8c3f-8d) 00:01:00:01:28:94:09:7b:fa:16:3e:f1:a9:da
> 2021-07-28T12:26:38.805023+00:00 pub1-network-3 dnsmasq-dhcp[3765807]:
> DHCPADVERTISE(tap67fa8c3f-8d) 00:01:00:01:28:94:09:7b:fa:16:3e:f1:a9:da no
> addresses available
>
> - Server side:
> /var/lib/neutron/dhcp/dcf25c41-9057-4bc2-8475-a2e3c5d8c662/host:fa:16:3e:f1:a9:da,tag:dhcpv6,host-<redacted>--143.dc3-a.pub1.infomaniak.cloud.,[<redacted>::143]
> /var/lib/neutron/dhcp/dcf25c41-9057-4bc2-8475-a2e3c5d8c662/leases:1627481056
> 1056025050 2001:1600:10:100::143 host-<redacted>--143
> 00:01:00:01:28:94:03:11:fa:16:3e:f1:a9:da
So dnsmasq is wrongly configured to take the DUID into account, even if
it does not matter for the address selection, because the address is
fixed?
> We see here that DHCPv6 fails because the DUID sent by the distro isn't the
> same as the initial build of the VM:
Well, the pending change in network machinery will scramble the DUID
anyway. So you can't rely on it.
Bastian
--
Extreme feminine beauty is always disturbing.
-- Spock, "The Cloud Minders", stardate 5818.4
