<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hi Albert,<br><br></div>Thanks for your suggestion.<br><br></div>I believe it is not in the slaac mode and in dhcpv6 only. <br><br></div>I confirmed with below things.<br><br></div>1) Router advertise, solicit, request things are happening while every client getting connected.<br></div>2) The bit Managed address configuration is set. Checked through wireshark. It will be set<br></div>in DHCPv6 only and not for slaac.<br><br></div>If you believe still it is in slaac mode, Please tell the config changes to make<br></div>dnsmasq run as a dhcpv6 server.<br><br></div>Thanks,<br></div>Gopi krishna M<br><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 8:20 PM, Albert ARIBAUD <span dir="ltr"><<a href="mailto:albert.aribaud@free.fr" target="_blank">albert.aribaud@free.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Le Wed, 25 May 2016 19:17:31 +0530<br>
Gopi Krishna M <<a href="mailto:gopi.k@msystechnologies.com">gopi.k@msystechnologies.com</a>> a écrit:<br>
<span class=""><br>
> Hi All,<br>
><br>
> I have been using dnsmasq 2.70 vesrion as dhcp server for ipv4 and<br>
> ipv6. My lease file is not getting updated properly when<br>
> running dnsmasq. It is updating properly for ipv4 but not correct<br>
> for ipv6.<br>
><br>
> #cat /etc/dnsmasq_new.leases<br>
> 2082886681 00:80:48:4b:83:12 192.168.10.161 host-mysy *<br>
> duid 00:01:00:01:43:b8:34:78:00:80:a3:a0:bb:38<br>
</span>> 2082843195 1212908306 *18:2001:2002:2003:: **<br>
<span class="">> 00:01:00:01:00:80:10:7e:ea:09<br>
><br>
> It is marked as above and its actual lease ip is<br>
</span>> *2001:2002:2003::10a* but its not showing. Meanwhile even if we<br>
> connect multiple clients then the same *18:2001:2002:2003:: *is<br>
<span class="">> getting repeated. Meanwhile it is not showing the<br>
> proper mac also.<br>
><br>
> for your kind ref:<br>
><br>
> config file<br>
> # cat /etc/dnsmasq_gateway.conf<br>
> interface=lan0<br>
> except-interface=lo<br>
> bind-interfaces<br>
> dhcp-range=192.168.10.20, 192.168.10.254, 14h<br>
> dhcp-range=2001:2002:2003::105, 2001:2002:2003::110, 64, 14h<br>
> enable-ra<br>
><br>
> Interface IP: 192.168.10.1<br>
> IPv6: 2001:2002:2003::100<br>
><br>
> running as<br>
><br>
><br>
</span>> *dnsmasq -C /etc/dnsmasq_gateway.conf -l /etc/dnsmasq_new.leases*<br>
<span class="">> Please tell your suggestions.<br>
><br>
> Note: Clients are getting IPv4 and IPv6 properly. Everything is fine<br>
> apart from updating the lease file. Compiled for ARM(linux 3.10)<br>
><br>
> Thanks in advance.<br>
><br>
> Regards,<br>
> Gopi krishna M<br>
<br>
</span>(anyone feel free to correct me if I got the following wrong)<br>
<br>
You are using SLAAC for IPv6 configuration. In this mode, it is the<br>
client, not the DHCP server, which selects its own IPv6.<br>
<br>
Therefore there are no actual IPv6 leases: dnsmasq just informs the<br>
client about the /64 subnet under which the client, not dnsmasq, shall<br>
select its address; the client does not inform dnsmasq back.<br>
<br>
This is /probably/ why the actual address does not show up in the lease<br>
file.<br>
<br>
If you want dnsmasq to control which address the client receives (and<br>
possibly log this in the lease file) then you should use DHCPv6 rather<br>
than SLAAC.<br>
<br>
Amicalement,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Albert.<br>
</font></span></blockquote></div><br></div>
<br>
<p style="text-align:justify"><span lang="EN-US"><font size="1">DISCLAIMER</font></span></p>
<p style="text-align:justify"><font size="1"><span lang="EN-US">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 <a href="mailto:it@msystechnologies.com" target="_blank">it@msystechnologies.com</a>,
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.</span></font></p>
<font size="1"><span lang="EN-US">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 </span>all reasonable
precautions have been taken to ensure no viruses are present in this e-mail<span lang="EN-US">. </span>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</font>