From: Andrew Zaborowski <andrew.zaborowski@intel.com>
To: ell@lists.linux.dev
Subject: [PATCH 1/5] dhcp6: Include Client ID in Information-Request
Date: Fri, 30 Sep 2022 15:52:46 +0200 [thread overview]
Message-ID: <20220930135250.534296-1-andrew.zaborowski@intel.com> (raw)
The Reply parser requires that the Client ID be present in the Reply but
the server only includes that if the Information-Request included the
Client ID. RFC 8415 Section 18.2.6 has this to say about the Client ID:
"The client SHOULD include a Client Identifier option (see Section 21.2)
to identify itself to the server (however, see Section 4.3.1 of [RFC7844]
for reasons why a client may not want to include this option). If the
client does not include a Client Identifier option, the server will not
be able to return any client-specific options to the client, or the
server may choose not to respond to the message at all."
RFC 7833 Section 4.3.1 says this:
"When using stateless DHCPv6, clients wanting to protect their privacy
SHOULD NOT include client identifiers in their Information-request
messages. This will prevent the server from specifying client-specific
options if it is configured to do so, but the need for anonymity
precludes such options anyway."
---
The obvious alternative is to not include the Client ID and not require
it in the Reply validation, or make this configurable to avoid privacy
concerns. I'm happy to go with either of these options.
ell/dhcp6.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ell/dhcp6.c b/ell/dhcp6.c
index 2792ff2..0705a7b 100644
--- a/ell/dhcp6.c
+++ b/ell/dhcp6.c
@@ -738,6 +738,8 @@ static int dhcp6_client_send_information_request(struct l_dhcp6_client *client)
option_append_elapsed_time(builder, client->transaction_start_t);
option_append_option_request(builder, client->request_options,
DHCP6_STATE_REQUESTING_INFORMATION);
+ option_append_bytes(builder, DHCP6_OPTION_CLIENT_ID,
+ client->duid, client->duid_len);
information_request = dhcp6_message_builder_free(builder, false,
&information_request_len);
--
2.34.1
next reply other threads:[~2022-09-30 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 13:52 Andrew Zaborowski [this message]
2022-09-30 13:52 ` [PATCH 2/5] dhcp6: Fix emitting LEASE_OBTAINED in stateless mode Andrew Zaborowski
2022-09-30 13:52 ` [PATCH 3/5] netconfig: Enable stateless DHCP mode Andrew Zaborowski
2022-09-30 13:52 ` [PATCH 4/5] netconfig: Return SLAAC+DHCP6 DNS info from getters Andrew Zaborowski
2022-09-30 13:52 ` [PATCH 5/5] netconfig: Stop ongoing work on failure Andrew Zaborowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220930135250.534296-1-andrew.zaborowski@intel.com \
--to=andrew.zaborowski@intel.com \
--cc=ell@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).