[Dnsmasq-discuss] trouble with DHCPv6

[e9hack]

Hi,

I'm trying to test the latest test release with DHCPv6 support. My dnsmasq configuration
is for DHCP only. For known hosts, I assign fixed IPv4 addresses. My configuration file
contains statements like this:

dhcp-host=00:11:F6:xx:xx:xx,vdr,192.168.25.6

The host file contains a IPv4 and a IPv6 address for this host:

192.168.25.6 vdr
fdXX:XXXX:XXXX:XXXX:xxxx:xxff:fexx:xxxx vdr

The IPv6 address is the ULA prefix with the self configured part from the host.

If the host-file contains both addresses, dnsmasq denies the configured IPv4 address. The
log contains the following messages:

daemon.info dnsmasq-dhcp[2904]: DHCPREQUEST(br0) 192.168.25.6 00:11:F6:xx:xx:xx
daemon.info dnsmasq-dhcp[2904]: DHCPNAK(br0) 192.168.25.6 00:11:F6:xx:xx:xx address not
available
daemon.info dnsmasq-dhcp[2904]: DHCPDISCOVER(br0) 00:11:F6:xx:xx:xx
daemon.info dnsmasq-dhcp[2904]: DHCPOFFER(br0) 192.168.25.119 00:11:F6:xx:xx:xx
daemon.info dnsmasq-dhcp[2904]: DHCPREQUEST(br0) 192.168.25.119 00:11:F6:xx:xx:xx
daemon.info dnsmasq-dhcp[2904]: DHCPACK(br0) 192.168.25.119 00:11:F6:xx:xx:xx vdr
daemon.warn dnsmasq-dhcp[2904]: not giving name vdr.lan to the DHCP lease of
192.168.25.119 because the name exists in /var/hosts with address 192.168.25.6
daemon.warn dnsmasq-dhcp[2904]: not giving name vdr to the DHCP lease of 192.168.25.119
because the name exists in /var/hosts with address 192.168.25.6
daemon.info dnsmasq-dhcp[2904]: DHCPREQUEST(br0) 192.168.25.119 00:11:F6:xx:xx:xx
daemon.info dnsmasq-dhcp[2904]: DHCPACK(br0) 192.168.25.119 00:11:F6:xx:xx:xx vdr
daemon.warn dnsmasq-dhcp[2904]: not giving name vdr.lan to the DHCP lease of
192.168.25.119 because the name exists in /var/hosts with address 192.168.25.6
daemon.warn dnsmasq-dhcp[2904]: not giving name vdr to the DHCP lease of 192.168.25.119
because the name exists in /var/hosts with address 192.168.25.6

dnsmasq itself runs on ADSL router with IPv4 and IPv6 support. The IPv6 prefix is announce
with radvd.

If I remove the 'goto again' statement at the end of dhcp_update_configs(), I don't get
this problem.

Regards,
Hartmut