I have dnsmasq set to be a DHCPv6 and DHCPv6 server for my local
network. Here is the relevant part of the configuration:
My problem is that if a DHCPv6 client attempts to confirm an unknown
lease (from another network, for example if I unplug a computer from
vlan4 and plug it into vlan3), dnsmasq doesn't respond to the
DHCPCONFIRM messages that the client sends. I just get a long string of
until the client finally gives up and acquires a new lease from scratch.
This also happens if I connect a client to my network that was
previously connected to another network with a DHCPv6 lease. For DHCPv4
in the same situation, it works correctly and sends a DHCPNAK, causing
the client to retry from scratch immediately and get a new lease quickly
as described in the documentation for the "dhcp-authoritative" option.
It seems to me this ought to take place for DHCPv6 as well, preventing
the client from having to time out before obtaining a lease. Have I
configured something wrong or is there a bug?
Dnsmasq-discuss mailing list