Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Make DHCPv6 respond with Remote-ID (opt 37) (Joachim Tingvold)
----------------------------------------------------------------------
Message: 1
Date: Sun, 27 Apr 2025 20:02:03 +0200
From: Joachim Tingvold <joac...@tingvold.com>
To: dhcp-users@lists.isc.org
Subject: Make DHCPv6 respond with Remote-ID (opt 37)
Message-ID: <78b202e9-7aca-42ad-9142-055750a6e...@tingvold.com>
Content-Type: text/plain; charset=UTF-8; markup=markdown
Hi,
For DHCPv4, Remote-ID and Circuit-ID are both sub-options of option 82. This
means they are both included in responses by-default.
For DHCPv6, these are split into two separate options; option 18 (Interface-ID)
and option 37 (Remote-ID). By-default, only Interface-ID is included in
responses.
Is there a simple way to ?force? isc-dhcpd to include both options in all
responses? (and not just option 18).
My first stab was to do this:
if exists dhcp6.remote-id {
option dhcp6.remote-id = option dhcp6.remote-id;
}
? but that didn?t seem to change anything, at least that I could see.
--
Joachim
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 193, Issue 1
******************************************
