From: Alex Goodkind via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alex Goodkind <alex@goodkind.io>, tarick@bedeir.com
Subject: [pve-devel] [PATCH container 0/2] Add DHCPv6 DUID support to container interface query
Date: Sun, 23 Nov 2025 16:43:00 -0800 [thread overview]
Message-ID: <mailman.5.1763945056.399.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6732 bytes --]
From: Alex Goodkind <alex@goodkind.io>
To: pve-devel@lists.proxmox.com
Cc: tarick@bedeir.com, Alex Goodkind <alex@goodkind.io>
Subject: [PATCH container 0/2] Add DHCPv6 DUID support to container interface query
Date: Sun, 23 Nov 2025 16:43:00 -0800
Message-ID: <20251124004302.498297-1-alex@goodkind.io>
This patch series adds DHCPv6 DUID (DHCP Unique Identifier) support
to the container interface query API. The implementation retrieves the
DUID via networkctl and formats it according to RFC 8415 with the
appropriate type prefix.
The first patch extends the get_interfaces function to query networkctl
for DUID information and parse it into the proper format. The second
patch updates the API schema to include the duid field in the response.
This allows users to see the DHCPv6 DUID assigned to each
container network interface, which is necessary for setting up
static DHCPv6 leases programmatically and useful for network
management and debugging DHCPv6 configurations.
Note: When applying these patches, please preserve my email address
<alex@goodkind.io> in the Author field for proper attribution.
Previously, when I sent patches via the mailing list, the Author field
was rewritten to "Alex Goodkind via pve-devel <pve-devel@lists.proxmox.com>",
which prevented GitHub from correctly attributing the commits to my
account. Thank you!
Alex Goodkind (2):
lxc: add DHCPv6 DUID retrieval to get_interfaces
api: add duid field to container interface schema
src/PVE/API2/LXC.pm | 5 ++++
src/PVE/LXC.pm | 72 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 77 insertions(+)
--
2.43.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-11-24 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.5.1763945056.399.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alex@goodkind.io \
--cc=tarick@bedeir.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox