From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-container v3 14/17] net: report NIC plugs and removals to the SDN DHCP backends
Date: Tue, 20 Oct 2026 15:36:52 +0200 [thread overview]
Message-ID: <416ec56f-ebe6-4d62-adb8-b12d0420ffe3@proxmox.com> (raw)
In-Reply-To: <20261020080005.470757-15-h.laimer@proxmox.com>
Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>
On 10/20/26 10:02 AM, Hannes Laimer wrote:
> An SDN DHCP backend answers a guest NIC with the address IPAM holds
> for its MAC. A NIC joining its bridge now hands its MAC to the SDN
> plug, so the backend of its vnet can answer its first request.
> Deleting a veth also reports it as gone to the backends, since their
> state for an interface can outlive it.
>
> On a running container, a bridge change now pushes the DHCP mapping
> for the new vnet, as adding a NIC or changing its MAC already does.
>
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> src/PVE/LXC.pm | 13 +++++++++++--
> src/PVE/LXC/Config.pm | 3 ++-
> src/lxc-pve-poststop-hook | 6 +++---
> 3 files changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index 1f11490..c3cf9e7 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -1111,7 +1111,13 @@ sub net_tap_plug : prototype($$) {
> my $create_firewall_bridges = $net->{firewall} && PVE::Firewall::Helpers::needs_fwbr($bridge);
>
> PVE::Network::SDN::Zones::tap_plug(
> - $iface, $bridge, $tag, $create_firewall_bridges, $trunks, $rate,
> + $iface,
> + $bridge,
> + $tag,
> + $create_firewall_bridges,
> + $trunks,
> + $rate,
> + { mac => $hwaddr },
nit: I understand that this function already has quite a few arguments, but introducing a new
$opts and then setting the MAC there seems somewhat awkward as well? A matter of taste though, I
suppose..
> );
> PVE::Network::SDN::Zones::add_bridge_fdb($iface, $hwaddr, $bridge);
>
> @@ -1137,7 +1143,7 @@ sub update_net {
> || safe_string_ne($oldnet->{name}, $newnet->{name})
> ) {
>
> - PVE::Network::veth_delete($veth);
> + PVE::Network::SDN::Zones::veth_delete($veth);
>
> if (safe_string_ne($oldnet->{hwaddr}, $newnet->{hwaddr})) {
> eval {
> @@ -1192,6 +1198,9 @@ sub update_net {
> PVE::Network::SDN::Vnets::add_next_free_cidr(
> $newnet->{bridge}, $conf->{hostname}, $newnet->{hwaddr}, $vmid, undef, 1,
> );
> + PVE::Network::SDN::Vnets::add_dhcp_mapping(
> + $newnet->{bridge}, $newnet->{hwaddr}, $vmid, $conf->{hostname},
> + );
> }
> eval { PVE::LXC::net_tap_plug($veth, $newnet) };
> if (my $err = $@) {
> diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
> index 9823d00..b522413 100644
> --- a/src/PVE/LXC/Config.pm
> +++ b/src/PVE/LXC/Config.pm
> @@ -12,6 +12,7 @@ use PVE::GuestHelpers;
> use PVE::INotify;
> use PVE::JSONSchema qw(get_standard_option);
> use PVE::Network::SDN::Vnets;
> +use PVE::Network::SDN::Zones;
> use PVE::RESTEnvironment;
> use PVE::Tools;
>
> @@ -1696,7 +1697,7 @@ sub vmconfig_hotplug_pending {
> my $net = parse_lxc_network($conf->{$opt});
> PVE::LXC::kill_dhclients($vmid, $net->{name}) if $net->{'host-managed'};
>
> - PVE::Network::veth_delete("veth${vmid}i$netid");
> + PVE::Network::SDN::Zones::veth_delete("veth${vmid}i$netid");
> print "delete ips from $opt\n";
> eval {
> PVE::Network::SDN::Vnets::del_ips_from_mac(
> diff --git a/src/lxc-pve-poststop-hook b/src/lxc-pve-poststop-hook
> index c8bbb79..c5d1059 100755
> --- a/src/lxc-pve-poststop-hook
> +++ b/src/lxc-pve-poststop-hook
> @@ -11,7 +11,7 @@ use PVE::GuestHelpers;
> use PVE::LXC::Config;
> use PVE::LXC::Tools;
> use PVE::LXC;
> -use PVE::Network;
> +use PVE::Network::SDN::Zones;
> use PVE::RESTEnvironment;
> use PVE::Storage;
> use PVE::Tools;
> @@ -49,8 +49,8 @@ PVE::LXC::Tools::lxc_hook(
> my $ind = $1;
> my $net = PVE::LXC::Config->parse_lxc_network($conf->{$k});
> next if $net->{type} ne 'veth';
> - # veth_delete tests with '-d /sys/class/net/$name' before running the command
> - PVE::Network::veth_delete("veth${vmid}i$ind");
> + # reports the unplug and deletes the veth only where it still exists
> + PVE::Network::SDN::Zones::veth_delete("veth${vmid}i$ind");
> }
>
> my $config_updated = 0;
next prev parent reply other threads:[~2026-10-20 13:36 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 7:59 [PATCH container/docs/manager/network/proxmox{-ebpf,-perl-rs}/qemu-server v3 00/17] sdn: implement DHCP for all zones using eBPF Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-ebpf v3 01/17] dhcp: add the per-tap DHCPv4 responder program Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-ebpf v3 02/17] dhcp: add the subsystem that loads the responder and keeps its records Hannes Laimer
2026-10-20 13:09 ` Stefan Hanreich
2026-10-21 7:09 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-perl-rs v3 03/17] pve-rs: sdn: add bindings for the eBPF DHCP responder Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 7:32 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 04/17] sdn: dhcp: replace a stale dnsmasq reservation instead of dropping it Hannes Laimer
2026-10-20 13:15 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 05/17] sdn: dhcp: update reservations when ip mappings change Hannes Laimer
2026-10-20 13:42 ` Stefan Hanreich
2026-10-21 7:21 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 06/17] sdn: ipam: key the MAC cache by lower-case MAC, stop caching misses Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 6:17 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 07/17] sdn: dhcp: make the lease time configurable per subnet Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 08/17] sdn: dhcp: require a backend only if a zone on this node uses it Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 09/17] sdn: dhcp: add an eBPF backend answering on each guest interface Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 6:16 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 10/17] sdn: zones: report interface plugs and unplugs to the DHCP backends Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 11/17] sdn: dhcp: push IP mapping edits to the guest's node Hannes Laimer
2026-10-20 13:09 ` Stefan Hanreich
2026-10-21 6:44 ` Hannes Laimer
2026-10-20 8:00 ` [PATCH pve-network v3 12/17] sdn: zones: allow the ebpf DHCP backend on every zone type Hannes Laimer
2026-10-20 8:00 ` [PATCH qemu-server v3 13/17] network: sdn: keep the DHCP backends current on guest NICs Hannes Laimer
2026-10-20 13:38 ` Stefan Hanreich
2026-10-20 8:00 ` [PATCH pve-container v3 14/17] net: report NIC plugs and removals to the SDN DHCP backends Hannes Laimer
2026-10-20 13:36 ` Stefan Hanreich [this message]
2026-10-21 7:29 ` Hannes Laimer
2026-10-20 8:00 ` [PATCH pve-manager v3 15/17] ui: sdn: add zone DHCP backend selector and subnet DHCP options Hannes Laimer
2026-10-20 13:19 ` Stefan Hanreich
2026-10-20 8:00 ` [PATCH pve-manager v3 16/17] sdn: bring up the DHCP backends at boot before the guests start Hannes Laimer
2026-10-20 13:21 ` Stefan Hanreich
2026-10-21 7:17 ` Hannes Laimer
2026-10-20 8:00 ` [PATCH pve-docs v3 17/17] sdn: dhcp: add eBPF backend section Hannes Laimer
2026-10-20 13:11 ` [PATCH container/docs/manager/network/proxmox{-ebpf,-perl-rs}/qemu-server v3 00/17] sdn: implement DHCP for all zones using eBPF Stefan Hanreich
2026-10-21 7:35 ` Hannes Laimer
2026-10-21 8:46 ` superseded: " Hannes Laimer
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=416ec56f-ebe6-4d62-adb8-b12d0420ffe3@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.