From: Hannes Laimer <h.laimer@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-network v3 11/17] sdn: dhcp: push IP mapping edits to the guest's node
Date: Wed, 21 Oct 2026 08:44:29 +0200 [thread overview]
Message-ID: <4aa82210-d5e2-4fe8-8489-26216796adac@proxmox.com> (raw)
In-Reply-To: <ce2ee4ff-affc-4cf4-97da-0a9c421ee9f3@proxmox.com>
On 2026-10-20 15:10, Stefan Hanreich wrote:
> On 10/20/26 10:02 AM, Hannes Laimer wrote:
>> IP mappings live in the cluster-wide IPAM and can be edited through
>> the API on any node. The DHCP backends hold their copy on each node,
>> dnsmasq in a reservation file and the ebpf responder in a kernel map.
>> An edit only updated the backend of the node it was made on, so a
>> guest on another node kept getting the old mapping.
>>
>> The new endpoint POST /nodes/{node}/sdn/dhcp-mapping updates the
>> mapping of one MAC on that node from the current records. An edit
>> made on a node other than the guest's calls it on the guest's node.
>> Only that node answers the guest's DHCP requests, so no other node is
>> called. The others catch up when the guest starts on one of them.
>>
>> The call runs in the background, so the request returns without
>> waiting on the other node. A call that fails logs its error to the
>> journal of the node the edit was made on. One that gets no answer is
>> stopped after a minute. The record stays as written either way, and
>> the guest's node picks it up at the latest when the guest next starts
>> there.
>>
>> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
>> ---
>> src/PVE/API2/Network/SDN/Ips.pm | 3 +
>> src/PVE/API2/Network/SDN/Nodes/Status.pm | 37 ++++++++++
>> src/PVE/Network/SDN/Dhcp.pm | 74 +++++++++++++++++++
>> src/test/run_test_vnets_blackbox.pl | 90 ++++++++++++++++++++++++
>> 4 files changed, 204 insertions(+)
>>
>> diff --git a/src/PVE/API2/Network/SDN/Ips.pm b/src/PVE/API2/Network/SDN/Ips.pm
>> index d7b682dd..5b45de7c 100644
>> --- a/src/PVE/API2/Network/SDN/Ips.pm
>> +++ b/src/PVE/API2/Network/SDN/Ips.pm
>> @@ -47,6 +47,7 @@ __PACKAGE__->register_method({
>> die "$@\n" if $@;
>>
>> PVE::Network::SDN::Dhcp::update_mapping($vnet, $mac);
>> + PVE::Network::SDN::Dhcp::notify_guest_node($vnet, $mac);
>>
>> return undef;
>> },
>> @@ -85,6 +86,7 @@ __PACKAGE__->register_method({
>> PVE::Network::SDN::Vnets::add_ip($vnet, $ip, '', $mac, undef);
>>
>> PVE::Network::SDN::Dhcp::update_mapping($vnet, $mac);
>> + PVE::Network::SDN::Dhcp::notify_guest_node($vnet, $mac);
>>
>> return undef;
>> },
>> @@ -138,6 +140,7 @@ __PACKAGE__->register_method({
>> die "$error\n" if $error;
>>
>> PVE::Network::SDN::Dhcp::update_mapping($vnet, $mac);
>> + PVE::Network::SDN::Dhcp::notify_guest_node($vnet, $mac);
>>
>> return undef;
>> },
>> diff --git a/src/PVE/API2/Network/SDN/Nodes/Status.pm b/src/PVE/API2/Network/SDN/Nodes/Status.pm
>> index 7977e0c8..fe750a85 100644
>> --- a/src/PVE/API2/Network/SDN/Nodes/Status.pm
>> +++ b/src/PVE/API2/Network/SDN/Nodes/Status.pm
>> @@ -9,6 +9,9 @@ use PVE::API2::Network::SDN::Nodes::Vnets;
>>
>> use PVE::JSONSchema qw(get_standard_option);
>>
>> +use PVE::Network::SDN::Vnets;
>> +use PVE::Network::SDN::Dhcp;
>> +
>> use PVE::RESTHandler;
>> use base qw(PVE::RESTHandler);
>>
>> @@ -27,6 +30,40 @@ __PACKAGE__->register_method({
>> path => 'vnets',
>> });
>>
>> +__PACKAGE__->register_method({
>> + name => 'dhcp_mapping',
>> + path => 'dhcp-mapping',
>> + method => 'POST',
>> + description =>
>> + 'Re-apply the DHCP mapping of a MAC address on this node from the current records.',
>> + permissions => {
>> + check => ['perm', '/sdn/zones/{zone}/{vnet}', ['SDN.Allocate']],
>> + },
>> + protected => 1,
>> + proxyto => 'node',
>> + parameters => {
>> + additionalProperties => 0,
>> + properties => {
>> + node => get_standard_option('pve-node'),
>> + zone => get_standard_option('pve-sdn-zone-id'),
>> + vnet => get_standard_option('pve-sdn-vnet-id'),
>> + mac => get_standard_option('mac-addr'),
>> + },
>> + },
>> + returns => { type => 'null' },
>> + code => sub {
>> + my ($param) = @_;
>> +
>> + my $vnet = PVE::Network::SDN::Vnets::get_vnet($param->{vnet}, 1);
>> + die "vnet '$param->{vnet}' does not exist in zone '$param->{zone}'\n"
>> + if !$vnet || $vnet->{zone} ne $param->{zone};
>> +
>> + PVE::Network::SDN::Dhcp::update_mapping($param->{vnet}, $param->{mac});
>> +
>> + return undef;
>> + },
>> +});
>> +
>> __PACKAGE__->register_method({
>> name => 'sdnindex',
>> path => '',
>> diff --git a/src/PVE/Network/SDN/Dhcp.pm b/src/PVE/Network/SDN/Dhcp.pm
>> index cf805a03..1f43745f 100644
>> --- a/src/PVE/Network/SDN/Dhcp.pm
>> +++ b/src/PVE/Network/SDN/Dhcp.pm
>> @@ -3,6 +3,8 @@ package PVE::Network::SDN::Dhcp;
>> use strict;
>> use warnings;
>>
>> +use POSIX qw();
>> +
>> use PVE::Cluster;
>>
>> use PVE::Network::SDN;
>> @@ -86,6 +88,78 @@ sub guest_nics {
>> return $nics;
>> }
>>
>> +sub guest_node_by_mac {
>> + my ($vnetid, $mac) = @_;
>> +
>> + for my $nic (guest_nics()->@*) {
>> + return $nic->{node}
>> + if lc($nic->{mac} // '') eq lc($mac) && $nic->{bridge} eq $vnetid;
>> + }
>> +
>> + return undef;
>> +}
>
> seems like we're always (or at least most of the time) querying by MAC
> so would assembling a hash keyed by MAC addresses in the first place be sensible?
>
yes, keyed by lc mac with a list per mac since one can appear on several
guests
will do in v4
>
>> +sub notify_guest_node {
>> + my ($vnetid, $mac) = @_;
>> +
>> + return if !$mac;
>> +
>> + # best effort like the push itself, since the record is written by now
>> + my ($zoneid, $node) = eval {
>> + my $vnet = PVE::Network::SDN::Vnets::get_vnet($vnetid, 1);
>> + return if !$vnet;
>> +
>> + my $zone = PVE::Network::SDN::Zones::get_zone($vnet->{zone}, 1);
>> + return if !$zone || !$zone->{ipam} || !$zone->{dhcp};
>> +
>> + return ($vnet->{zone}, guest_node_by_mac($vnetid, $mac));
>> + };
>> + if ($@) {
>> + warn "could not find the node to push the dhcp mapping of $mac to: $@";
>> + return;
>> + }
>> + return if !$node || $node eq PVE::INotify::nodename();
>> +
>> + # double fork, the grandchild is reparented to init so nothing on
>> + # the request path ever waits on it
>> + my $pid = fork();
>> + if (!defined($pid)) {
>> + warn "could not fork for the dhcp mapping push to $node: $!\n";
>> + return;
>> + }
>> + if ($pid) {
>> + waitpid($pid, 0);
>> + return;
>> + }
>> +
>> + POSIX::setsid();
>> + my $child = fork();
>> + POSIX::_exit(1) if !defined($child);
>> + POSIX::_exit(0) if $child;
>> +
>> + # nothing of the request stays with the push, and since the daemon's
>> + # stderr is closed a failed push reports through the journal
>> + open(STDIN, '<', '/dev/null') or POSIX::_exit(1);
>> + open(STDOUT, '>', '/dev/null') or POSIX::_exit(1);
>> + open(STDERR, '|-', 'logger', '-t', 'pve-sdn', '-p', 'daemon.warning')
>> + or POSIX::_exit(1);
>> + # a node that takes the connection but never answers must not keep the
>> + # push around
>> + exec(
>> + 'timeout',
>> + '60',
>> + 'pvesh',
>> + 'create',
>> + "/nodes/$node/sdn/dhcp-mapping",
>> + '--zone',
>> + $zoneid,
>> + '--vnet',
>> + $vnetid,
>> + '--mac',
>> + $mac,
>> + ) or POSIX::_exit(1);
>> +}
>> +
>
> There've been efforts of moving away from pvesh - see my other patch
> series introducing the api client instead of calling pvesh here:
>
[1]
> https://lore.proxmox.com/all/20260709140625.275618-1-s.hanreich@proxmox.com/
>
> Might be the better option here as well?
i did consider that, but at the time it seemed like "a lot" for
something where a different precedent exists already, but yes, `pvesh`
did seem *meh* here. also wasn't aware of [1]
>
> Also, there is proxyto_callback which we could use to proxy to the correct
> node in the first place?
yes, this should work, and be the better approach here. the only thing
it introduces is a cluster endpoint whose edit fails when another node
isn't reachable, which we don't have yet.. but tbf, it's niche, and
arguably also correct here
will include in v4!
>
>> sub tap_plug {
>> my ($bridge, $iface, $mac) = @_;
>>
>> diff --git a/src/test/run_test_vnets_blackbox.pl b/src/test/run_test_vnets_blackbox.pl
>> index 783d0d47..9a4dbb9c 100755
>> --- a/src/test/run_test_vnets_blackbox.pl
>> +++ b/src/test/run_test_vnets_blackbox.pl
>> @@ -49,6 +49,7 @@ sub clear_test_state {
>> dnsmasq_calls => [],
>> ebpf_calls => [],
>> order => [],
>> + notify_calls => [],
>> warnings => [],
>> ipam_config => {
>> 'ids' => {
>> @@ -238,6 +239,11 @@ $mocked_sdn_dhcp_dnsmasq->mock(
>> update_lease => sub { },
>> );
>>
>> +my $mocked_sdn_dhcp = Test::MockModule->new('PVE::Network::SDN::Dhcp');
>> +$mocked_sdn_dhcp->mock(
>> + notify_guest_node => sub { push $test_state->{notify_calls}->@*, [@_]; },
>> +);
>> +
>> my $mocked_pve_rs_dhcp = Test::MockModule->new('PVE::RS::SDN::Dhcp');
>> $mocked_pve_rs_dhcp->mock(
>> detach => sub {
>> @@ -1280,6 +1286,90 @@ sub test_dhcp_backend_needed_per_node {
>>
>> run_test(\&test_dhcp_backend_needed_per_node);
>>
>> +sub test_mapping_push_target {
>> + my $test_name = (split(/::/, (caller(0))[3]))[-1];
>> + my $zoneid = "TESTZONE";
>> + my $vnetid = "testvnet";
>> + my $mac = "da:65:8f:18:9b:6f";
>> +
>> + create_zone({
>> + type => "simple",
>> + dhcp => "dnsmasq",
>> + ipam => "pve",
>> + zone => $zoneid,
>> + });
>> + create_vnet({
>> + type => "vnet",
>> + zone => $zoneid,
>> + vnet => $vnetid,
>> + });
>> + create_subnet({
>> + type => "subnet",
>> + vnet => $vnetid,
>> + subnet => "10.0.0.0/24",
>> + gateway => "10.0.0.1",
>> + });
>> +
>> + # the guest behind a MAC is found by its NIC on the vnet, and the config
>> + # writes the MAC in upper case
>> + $test_state->{vmlist} = {
>> + ids => {
>> + 100 => { type => 'qemu', node => 'other' },
>> + 101 => { type => 'lxc', node => 'third' },
>> + },
>> + };
>> + $test_state->{guest_nets} = {
>> + 1 => { net0 => "virtio=$mac,bridge=$vnetid" },
>> + 100 => { net0 => "virtio=" . uc($mac) . ",bridge=$vnetid" },
>> + 101 => { net0 => "name=eth0,bridge=vmbr0,hwaddr=00:11:22:33:44:55" },
>> + };
>> + is(
>> + PVE::Network::SDN::Dhcp::guest_node_by_mac($vnetid, $mac),
>> + 'other',
>> + "$test_name: the MAC resolves to the node of its guest, a guest the list lacks is skipped",
>> + );
>> + is(
>> + PVE::Network::SDN::Dhcp::guest_node_by_mac($vnetid, '00:11:22:33:44:55'),
>> + undef,
>> + "$test_name: a MAC on another bridge does not resolve",
>> + );
>> + is(
>> + PVE::Network::SDN::Dhcp::guest_node_by_mac($vnetid, '00:11:22:33:44:66'),
>> + undef,
>> + "$test_name: an unknown MAC does not resolve",
>> + );
>> +
>> + # every mapping edit through the API pokes the guest's node once
>> + $test_state->{notify_calls} = [];
>> + create_ip({
>> + zone => $zoneid,
>> + vnet => $vnetid,
>> + mac => $mac,
>> + ip => "10.0.0.50",
>> + });
>> + update_ip({
>> + zone => $zoneid,
>> + vnet => $vnetid,
>> + mac => $mac,
>> + ip => "10.0.0.51",
>> + });
>> + delete_ip({
>> + zone => $zoneid,
>> + vnet => $vnetid,
>> + mac => $mac,
>> + ip => "10.0.0.51",
>> + });
>> + eq_or_diff(
>> + $test_state->{notify_calls},
>> + [[$vnetid, $mac], [$vnetid, $mac], [$vnetid, $mac]],
>> + "$test_name: create, edit and delete each poke the guest's node",
>> + );
>> + delete $test_state->{vmlist};
>> + delete $test_state->{guest_nets};
>> +}
>> +
>> +run_test(\&test_mapping_push_target);
>> +
>> sub test_ipam_cache_misses {
>> my $test_name = (split(/::/, (caller(0))[3]))[-1];
>> my $zoneid = "TESTZONE";
>
>
>
>
>
next prev parent reply other threads:[~2026-10-21 6:44 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 [this message]
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
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=4aa82210-d5e2-4fe8-8489-26216796adac@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox