From: Anshu Kumari <anskuma@redhat.com>
To: passt-dev@passt.top, sbrivio@redhat.com, anskuma@redhat.com
Cc: david@gibson.dropbear.id.au, jmaloy@redhat.com, lvivier@redhat.com
Subject: Re: [PATCH 0/3] [PATCH 0/3] dhcpv6: Add --dhcpv6-opt for custom DHCPv6 options
Date: Thu, 4 Jun 2026 16:30:18 +0530 [thread overview]
Message-ID: <CADJNnVLMxefWwyUpo4GNWnTVyb+UKJFwKq1NMvHc1TY_NvWamg@mail.gmail.com> (raw)
In-Reply-To: <20260604105150.1977905-1-anskuma@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
Following the current changes, future work will involve adding support for
options 138 and 139. I have not included these in this patch series because
the parsing for both requires significant code changes, which I believe
would be too much to review at once.
Regards,
Anshu
On Thu, Jun 4, 2026 at 4:22 PM Anshu Kumari <anskuma@redhat.com> wrote:
> This series adds a --dhcpv6-opt CODE,VALUE command-line option to
> inject custom options into DHCPv6 replies, complementing the existing
> --dhcp-opt support for DHCPv4.
>
> The primary use case is UEFI HTTP Boot, which requires Vendor Class
> (option 16) with the correct enterprise-number + length-prefixed wire
> encoding per RFC 8415 Section 21.16, and Boot File URL (option 59).
>
> Value formats are determined automatically from the option code via a
> type table. Supported types include plain strings, IPv6
> addresses (single and list), 8/16/32-bit integers, vendor class
> (ENTERPRISE:DATA), and length-prefixed string lists.
>
> Patch 1 adds the CLI flag, storage, and basic man page entry.
> Patch 2 adds the type table and binary parser for all supported types.
> Patch 3 injects the parsed options into DHCPv6 reply packets.
>
> Anshu Kumari (3):
> conf: Add --dhcpv6-opt command-line option
> dhcpv6: Add option type table and value parser
> dhcpv6: Inject custom options into DHCPv6 replies
>
> conf.c | 26 ++++-
> dhcpv6.c | 295 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> dhcpv6.h | 1 +
> passt.1 | 30 ++++++
> passt.h | 16 +++
> 5 files changed, 367 insertions(+), 1 deletion(-)
>
> --
> 2.54.0
>
>
[-- Attachment #2: Type: text/html, Size: 2165 bytes --]
prev parent reply other threads:[~2026-06-04 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 10:51 Anshu Kumari
2026-06-04 10:51 ` [PATCH 1/3] conf: Add --dhcpv6-opt command-line option Anshu Kumari
2026-06-04 10:51 ` [PATCH 2/3] dhcpv6: Add option type table and value parser Anshu Kumari
2026-06-04 10:51 ` [PATCH 3/3] dhcpv6: Inject custom options into DHCPv6 replies Anshu Kumari
2026-06-04 11:00 ` Anshu Kumari [this message]
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=CADJNnVLMxefWwyUpo4GNWnTVyb+UKJFwKq1NMvHc1TY_NvWamg@mail.gmail.com \
--to=anskuma@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).