[Dnsmasq-discuss] dhcpv6 duid gen

[Vladislav Grishenko]

> I wonder if the solution might be to just have a
> duid-override = <enterprise number>, <hex data>
> configuration which suppresses storing anything in the lease file  and
just
> uses a type-2 DUID in the obvious way?

Ok, and it can be even more easy - allow specify u_int64_t value and use it
with DUID-LL+27 ether type (eui64).
duid-override=<eui64>

> configuration which suppresses storing anything in the lease file  and
just
> uses a type-2 DUID in the obvious way?
Storing is allowed, but until reboot...

And what about traversing over ethernet-like interfaces only?
Actually, for me, it would be more handy than to implement own duid
generation and storing it in conf.
The root issue was in sit (6to4 tunnels) interfaces, which has no hwaddr to
be used as duid ll source.

Best Regards, Vladislav Grishenko


> -----Original Message-----
> From: Simon Kelley [mailto:simon at thekelleys.org.uk]
> Sent: Thursday, March 01, 2012 5:16 PM
> To: Vladislav Grishenko
> Cc: dnsmasq-discuss at lists.thekelleys.org.uk
> Subject: Re: dhcpv6 duid gen
> 
> On 29/02/12 23:26, Vladislav Grishenko wrote:
> > Little additions:
> >
> >> Allowing to specify from options would be useful too, eg. for
> >> multiple dnsmasq instances
> >
> > Per RFC3315 "A DHCP client that generates a DUID-LLT using this (using
> > sort
>                        ^^^^^^^
> 
> > of time source) mechanism MUST provide an administrative interface
> > that replaces the existing DUID with a newly-generated DUID-LLT."
> >
> >
> 
>  >> Hmm, I wonder if
>  >> "stop dnsmasq, edit /var/lib/misc/dnsmasq.leases, start dnsmasq"
>  >> counts as an administrative interface?
> 
>  > sure doesn't. in embedded there's no persistent storage for such  >
files
> other than /tmp, so under some circumstances file can be lost >  >
(reboot,
> fast reinit, etc).
>  > due hashing, there's a kind of guarantee that dhcpv4 client will get  >
his
> leases back, but not for dhcpv6 guid.
> 
> 
> I wonder if the solution might be to just have a
> 
> duid-override = <enterprise number>, <hex data>
> 
> configuration which suppresses storing anything in the lease file  and
just
> uses a type-2 DUID in the obvious way?
> 
> Cheers,
> 
> Simon.