[Dnsmasq-discuss] dnsmasq lease file not updating properly

[Gopi Krishna M]

Hi Albert,

Thanks for your suggestion.

I believe it is not in the slaac mode and in dhcpv6 only.

I confirmed with below things.

1) Router advertise, solicit, request things are happening while every
client getting connected.
2) The bit Managed address configuration is set. Checked through wireshark.
It will be set
in DHCPv6 only and not for slaac.

If you believe still it is in slaac mode, Please tell the config changes to
make
dnsmasq run as a dhcpv6 server.

Thanks,
Gopi krishna M


On Wed, May 25, 2016 at 8:20 PM, Albert ARIBAUD <albert.aribaud at free.fr>
wrote:

> Hi,
>
> Le Wed, 25 May 2016 19:17:31 +0530
> Gopi Krishna M <gopi.k at msystechnologies.com> a écrit:
>
> > Hi All,
> >
> > I have been using dnsmasq 2.70 vesrion as dhcp server for ipv4 and
> > ipv6. My lease file is not getting updated properly when
> > running dnsmasq. It is updating properly for ipv4  but not correct
> > for ipv6.
> >
> >  #cat /etc/dnsmasq_new.leases
> > 2082886681 00:80:48:4b:83:12 192.168.10.161 host-mysy *
> > duid 00:01:00:01:43:b8:34:78:00:80:a3:a0:bb:38
> > 2082843195 1212908306 *18:2001:2002:2003:: **
> > 00:01:00:01:00:80:10:7e:ea:09
> >
> > It is marked as above and its actual lease ip is
> > *2001:2002:2003::10a* but its not showing. Meanwhile even if we
> > connect multiple clients then the same *18:2001:2002:2003:: *is
> > getting repeated. Meanwhile it is not showing the
> > proper mac also.
> >
> > for your kind ref:
> >
> > config file
> > # cat /etc/dnsmasq_gateway.conf
> > interface=lan0
> > except-interface=lo
> > bind-interfaces
> > dhcp-range=192.168.10.20, 192.168.10.254, 14h
> > dhcp-range=2001:2002:2003::105, 2001:2002:2003::110, 64, 14h
> > enable-ra
> >
> > Interface IP: 192.168.10.1
> > IPv6: 2001:2002:2003::100
> >
> > running as
> >
> >
> > *dnsmasq -C /etc/dnsmasq_gateway.conf -l /etc/dnsmasq_new.leases*
> > Please tell your suggestions.
> >
> > Note: Clients are getting IPv4 and IPv6 properly. Everything is fine
> > apart from updating the lease file. Compiled for ARM(linux 3.10)
> >
> > Thanks in advance.
> >
> > Regards,
> > Gopi krishna M
>
> (anyone feel free to correct me if I got the following wrong)
>
> You are using SLAAC for IPv6 configuration. In this mode, it is the
> client, not the DHCP server, which selects its own IPv6.
>
> Therefore there are no actual IPv6 leases: dnsmasq just informs the
> client about the /64 subnet under which the client, not dnsmasq, shall
> select its address; the client does not inform dnsmasq back.
>
> This is /probably/ why the actual address does not show up in the lease
> file.
>
> If you want dnsmasq to control which address the client receives (and
> possibly log this in the lease file) then you should use DHCPv6 rather
> than SLAAC.
>
> Amicalement,
> --
> Albert.
>

-- 


DISCLAIMER

The information in this e-mail is confidential and may be subject to legal 
privilege. It is intended solely for the addressee. Access to this e-mail 
by anyone else is unauthorized. If you have received this communication in 
error, please address with the subject heading "Received in error," send to 
it at msystechnologies.com,  then delete the e-mail and destroy any copies of 
it. If you are not the intended recipient, any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on it, 
is prohibited and may be unlawful. The views, opinions, conclusions and 
other information expressed in this electronic mail and any attachments are 
not given or endorsed by the company unless otherwise indicated by an 
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free, 
as information could be intercepted, corrupted, amended, lost, destroyed, 
arrive late or incomplete, or contain viruses, though all reasonable 
precautions have been taken to ensure no viruses are present in this e-mail. 
As our company cannot accept responsibility for any loss or damage arising 
from the use of this e-mail or attachments we recommend that you subject 
these to your virus checking procedures prior to use
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20160526/76e7b8e3/attachment.html>