[Dnsmasq-discuss] dhcpv6 problem with static allocations and "no addresses available"

Carlos Carvalho carlos at fisica.ufpr.br
Thu Oct 22 23:58:45 BST 2015


Simon Kelley (simon at thekelleys.org.uk) wrote on Thu, Oct 22, 2015 at 08:20:48PM BRST:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> 
> 
> On 22/10/15 21:05, Carlos Carvalho wrote:
> 
> > What if, with an id* declaration, dnsmasq accepts any DUID the
> > first time but refuses other requests with different DUIDs? This
> > hypothesis explains the events above and all others I've seen.
> > However it contradicts what Simon says, that the hardware address
> > is enough to identify a client.
> 
> I should clarify: the hardware address is enough to identify the
> client, but if the dhcp-host includes a DUID _that_has_to_match_as_well.

Yes, but I'm talking explicitly about id:*. With it dnsmasq accepts any DUID
the first time but if the same client presents another DUID later dnsmasq
refuses the declared address. If there are dynamic ones available it'll give
one to the client, otherwise it bounces with "no available addresses". This
means that dnsmasq is taking history into account, not only the hardware
address. I think it should completely ignore the DUID if the dhcp-host has
id:*.

The manual says:

      For DHCPv4, the  special option id:* means "ignore any client-id
      and  use  MAC  addresses  only."  This  is  useful when a client
      presents a client-id sometimes but not others.

How do I do the same for DHCPv6 as well? I need it for both protocols, for the
same reason.



More information about the Dnsmasq-discuss mailing list