Discussion:
[Dnsmasq-discuss] client-identifier in server reply
Reddeiah Raju Konduru
2017-02-10 01:22:16 UTC
Permalink
Hi,

I am using dnsmasq 2.72. In dhclient after setting client identifier to
device mac address, I could see client-identifier option in DISCOVER and
REQUEST messages. But dhcp server(dnsmasq) not setting client identifier
option in OFFER and ACK replies.

As per RFC 6842 Section 3, If client is sending client-identifier server
also MUST include this option in reply.

Is this feature implemented in dnsmasq?
--
Thanks & Regards,
Reddaiah
Simon Kelley
2017-02-11 17:05:55 UTC
Permalink
Post by Reddeiah Raju Konduru
Hi,
I am using dnsmasq 2.72. In dhclient after setting client identifier to
device mac address, I could see client-identifier option in DISCOVER and
REQUEST messages. But dhcp server(dnsmasq) not setting client identifier
option in OFFER and ACK replies.
As per RFC 6842 Section 3, If client is sending client-identifier server
also MUST include this option in reply.
Is this feature implemented in dnsmasq?
No, it's not implemented, but it should be, four years after the RFC.


I just committed a patch to the git repo. It will be in 2.77.

Cheers,

Simon.
Reddeiah Raju Konduru
2017-02-13 22:18:06 UTC
Permalink
Hi Simon,

Can I get the access to patch?
If not possible let me know when 2.77 will be available to public?

Thanks,
Raju
Post by Simon Kelley
Post by Reddeiah Raju Konduru
Hi,
I am using dnsmasq 2.72. In dhclient after setting client identifier to
device mac address, I could see client-identifier option in DISCOVER and
REQUEST messages. But dhcp server(dnsmasq) not setting client identifier
option in OFFER and ACK replies.
As per RFC 6842 Section 3, If client is sending client-identifier server
also MUST include this option in reply.
Is this feature implemented in dnsmasq?
No, it's not implemented, but it should be, four years after the RFC.
I just committed a patch to the git repo. It will be in 2.77.
Cheers,
Simon.
_______________________________________________
Dnsmasq-discuss mailing list
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
--
Thanks & Regards,

Reddeiah Raju Konduru
+918095133903
Simon Kelley
2017-02-14 15:07:25 UTC
Permalink
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=88a77a78ad27ad
c3ed87b7ee603643d26cb896ee

There's a link that produces a patch file.


Cheers,

Simon.
Post by Reddeiah Raju Konduru
Hi Simon,
Can I get the access to patch? If not possible let me know when
2.77 will be available to public?
Thanks, Raju
On Sat, Feb 11, 2017 at 9:05 AM, Simon Kelley
Post by Reddeiah Raju Konduru
Hi,
I am using dnsmasq 2.72. In dhclient after setting client
identifier to device mac address, I could see client-identifier
option in DISCOVER and REQUEST messages. But dhcp server(dnsmasq)
not setting client identifier option in OFFER and ACK replies.
As per RFC 6842 Section 3, If client is sending client-identifier
server also MUST include this option in reply.
Is this feature implemented in dnsmasq?
No, it's not implemented, but it should be, four years after the RFC.
I just committed a patch to the git repo. It will be in 2.77.
Cheers,
Simon.
_______________________________________________ Dnsmasq-discuss
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
<http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss>
-- Thanks & Regards,
Reddeiah Raju Konduru +918095133903
_______________________________________________ Dnsmasq-discuss
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Simon Kelley
2017-04-11 11:14:26 UTC
Permalink
Post by Reddeiah Raju Konduru
Hi,
I am using dnsmasq 2.72. In dhclient after setting client identifier to
device mac address, I could see client-identifier option in DISCOVER and
REQUEST messages. But dhcp server(dnsmasq) not setting client identifier
option in OFFER and ACK replies.
As per RFC 6842 Section 3, If client is sending client-identifier server
also MUST include this option in reply.
Is this feature implemented in dnsmasq?
Could you elaborate a bit more on what you need this feature for. Since
implementing it, we've found one client which is broken by the presence
of client-ids and there may be more which mysteriously stop working.
Possibly only sending the client-id under certain circumstances may work
for you, without breaking sensitive clients.


Cheers,

Simon.

Loading...