From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH container/docs/manager/network/proxmox{,-perl-rs,-ve-rs}/qemu-server v6 00/17] sdn: implement DHCP for all zones using eBPF
Date: Thu, 12 Nov 2026 13:45:38 +0100 [thread overview]
Message-ID: <62562a47-0279-405c-9608-582bc85acb96@proxmox.com> (raw)
In-Reply-To: <20261105100316.449163-1-h.laimer@proxmox.com>
superseded-by:
https://lore.proxmox.com/pve-devel/20261112124201.2844423-1-h.laimer@proxmox.com/
On 2026-11-05 11:04, Hannes Laimer wrote:
> This series adds a second DHCP backend, ebpf, next to dnsmasq. A zone
> picks its backend. dnsmasq stays limited to simple zones, while ebpf
> answers on the guest's own interface and works on every zone type. A
> guest on a zone with the ebpf backend gets the address its NIC has in
> the IPAM. There is no daemon per zone and no lease file. The answers
> are held in the kernel and do not depend on the IPAM being reachable.
>
> The responder is a BPF program on the ingress of each guest interface
> of a zone with the ebpf backend. It answers a request from the record
> of that interface, and the exchange never reaches the bridge. A
> request whose client MAC is not the interface's own passes on
> unanswered. So a guest cannot read another guest's record, and a
> nested client does not get the outer guest's address.
>
> An edit through /cluster/sdn/vnets/{vnet}/ips is proxied to the
> guest's node and updates the backend there. The guest sees the change
> at its next renewal, so the lease time bounds how long an old answer
> survives. Subnets get a dhcp-lease-time property for both backends.
> Without it dnsmasq hands out infinite leases and the responder ten
> minutes. An apply attaches the responder to running guests, so a zone
> switched to ebpf serves them without a restart.
>
> Changes reach the kernel in the order they read their input. So no
> change overwrites a newer one with older input. A hotplug moves the
> interface before the guest config names the new bridge. An apply or an
> edit that read the older config in between leaves the moved interface
> as its plug left it. Once the config names the bridge the interface
> sits on, an apply also repairs an interface whose plug failed. An edit
> through the API whose update fails returns an error, with the mapping
> saved. Any other change that fails only warns, and what was served
> stays served. Nothing of the responder survives a reboot, so it is
> loaded again at boot before the guests start.
>
> Only DHCPv4 is answered. A request the guest tagged itself passes
> unanswered as well, so a trunk port keeps working as before. The
> request is answered on the guest interface, so the guest's firewall
> rules, its DHCP firewall option and its rate limit do not apply to it.
> The reply leaves through the interface's egress, where the rate limit
> shapes it. A request the responder does not answer passes on to the
> bridge and through the firewall as before. Mappings changed directly
> in an external IPAM are not picked up, as with dnsmasq.
>
> In patch order, the series adds
> - proxmox, a byte accessor for the MAC address type of
> proxmox-network-types, and the dhcp subsystem of proxmox-ebpf, a tc
> program answering on the guest interface and the per-interface map
> it answers from
> - pve-rs, the bindings
> - pve-network, the VXLAN and EVPN MTU taken from the underlay
> interface, the ebpf backend, the hooks that keep a backend current
> when a guest interface changes, and dhcp on every zone type
> - qemu-server and pve-container, the reports of a guest NIC coming,
> going or moving
> - pve-manager, the backend and subnet options in the UI, and the
> backends brought up at boot ahead of the guests
> - proxmox-ve-rs, the ebpf variant of the dhcp backend type
> - pve-docs, the MTU VXLAN and EVPN zones take from the underlay, and
> the documentation of the backend
>
> - proxmox applies on top of the proxmox-ebpf series [1]
> - pve-network, qemu-server and pve-docs apply on top of [2]
> - pve-rs needs proxmox-ebpf with the dhcp feature and
> proxmox-network-types with the byte accessor
> - pve-network needs pve-rs, at build and run time
> - qemu-server, pve-container and pve-manager need pve-network
> - proxmox-ve-config needs nothing, and proxmox-firewall needs its
> dependency on it bumped, since an older one fails to parse a zone
> with the ebpf backend and the firewall then cannot load its config
> An older pve-network fails its apply on the unknown backend, so every
> node needs the new one before a zone gets ebpf.
>
>
> v6:
> * like the ebpf-lib v8 [1] that this is based on, this moved into the
> proxmox workspace
> * rebased onto the ipam series v6 [2]
> * rebased onto current master
> * an apply repairs an interface whose plug failed, once it sits on
> the bridge its config names
> * a plug reads the zone's backend under the responder's lock, so an
> apply switching it meanwhile is not undone
> * a map replacement that cannot write every entry keeps the old maps
> * an API edit whose DHCP update fails returns an error
> * the bindings use the MAC address type of proxmox-network-types
> * docs: the MTU default of VXLAN and EVPN zones
>
> v5:
> * rebased onto ebpf-lib v5
> * the MAC cache and dnsmasq fixes moved to [2], as did running a
> mapping edit on the guest's node and the push on resume
> * a mapping edit only changes the answers on its own vnet
> * the VXLAN and EVPN bridges get the MTU that DHCP hands out, both
> take it from the underlay interface
> * a MAC change on the same vnet is no longer undone by an apply
> running meanwhile
>
> v4, thanks @Stefan!:
> * a mapping edit runs on the guest's node instead of being pushed to
> it, the node endpoint is gone
> * the MAC cache is read and written with lower-case keys, and its
> three fixes are three commits
> * the guest NIC list is keyed by MAC
> * add the missing proxmox-ve-rs patch, the ebpf variant of the dhcp
> backend type
> * reword log lines and warnings
> * (notes on patches with changes)
>
> v3:
> * drop the generation counter. Every change takes the responder's
> lock before it reads its input instead. An edit takes it
> exclusively
> * the resume at the end of a live migration pushes the guest's
> mappings again on the target, so an edit made during the migration
> reaches it
> * new first pve-network commit, a dnsmasq fix that replaces a stale
> reservation of another MAC instead of dropping it
> * no MTU option for a zone without an MTU, where v2 handed out 1500
> * a mapping edit without a MAC no longer reaches the backends
> * rewrite commit messages, cover letter and parts of the docs
> * rebase onto current master
>
> pre-build packages are on sani(`packages/ebpf-dhcp-v6`)
>
> [1] https://lore.proxmox.com/pve-devel/20261104172918.2643810-1-h.laimer@proxmox.com/
> [2] https://lore.proxmox.com/pve-devel/20261105093529.209052-1-h.laimer@proxmox.com/
>
>
> proxmox:
>
> Hannes Laimer (3):
> network-types: mac address: add an accessor for the bytes
> ebpf: dhcp: add the per-tap DHCPv4 responder program
> ebpf: dhcp: add the subsystem that loads the responder and keeps its
> records
>
> proxmox-ebpf/Cargo.toml | 5 +
> proxmox-ebpf/debian/control | 18 +
> proxmox-ebpf/src/bpf-shim/bpf/bpf_helpers.h | 1 +
> proxmox-ebpf/src/bpf-shim/linux/bpf.h | 3 +
> proxmox-ebpf/src/dhcp/bpf/dhcp.bpf.c | 400 ++++++
> proxmox-ebpf/src/dhcp/bpf/types.h | 24 +
> proxmox-ebpf/src/dhcp/mod.rs | 1219 +++++++++++++++++++
> proxmox-ebpf/src/dhcp/types.rs | 65 +
> proxmox-ebpf/src/lib.rs | 3 +
> proxmox-ebpf/src/subsystem.rs | 2 +-
> proxmox-ebpf/tests/common/mod.rs | 63 +-
> proxmox-ebpf/tests/dhcp.rs | 825 +++++++++++++
> proxmox-network-types/src/mac_address.rs | 13 +
> 13 files changed, 2636 insertions(+), 5 deletions(-)
> create mode 100644 proxmox-ebpf/src/dhcp/bpf/dhcp.bpf.c
> create mode 100644 proxmox-ebpf/src/dhcp/bpf/types.h
> create mode 100644 proxmox-ebpf/src/dhcp/mod.rs
> create mode 100644 proxmox-ebpf/src/dhcp/types.rs
> create mode 100644 proxmox-ebpf/tests/dhcp.rs
>
>
> proxmox-perl-rs:
>
> Hannes Laimer (1):
> pve-rs: sdn: add bindings for the eBPF DHCP responder
>
> pve-rs/Cargo.toml | 2 +
> pve-rs/Makefile | 3 +
> pve-rs/debian/control | 2 +
> pve-rs/src/bindings/sdn/dhcp.rs | 217 ++++++++++++++++++++++++++++++++
> pve-rs/src/bindings/sdn/mod.rs | 1 +
> 5 files changed, 225 insertions(+)
> create mode 100644 pve-rs/src/bindings/sdn/dhcp.rs
>
>
> pve-network:
>
> Hannes Laimer (6):
> sdn: zones: take the VXLAN and EVPN MTU from the underlay interface
> sdn: dhcp: make the lease time configurable per subnet
> sdn: dhcp: require a backend only if a zone on this node uses it
> sdn: dhcp: add an eBPF backend answering on each guest interface
> sdn: zones: report interface plugs and unplugs to the DHCP backends
> sdn: zones: allow the ebpf DHCP backend on every zone type
>
> debian/libpve-network-perl.prerm | 13 +
> src/PVE/API2/Network/SDN/Zones.pm | 11 +-
> src/PVE/Network/SDN/Dhcp.pm | 107 +-
> src/PVE/Network/SDN/Dhcp/Dnsmasq.pm | 3 +-
> src/PVE/Network/SDN/Dhcp/Ebpf.pm | 345 ++++++
> src/PVE/Network/SDN/Dhcp/Makefile | 2 +-
> src/PVE/Network/SDN/Dhcp/Plugin.pm | 24 +-
> src/PVE/Network/SDN/SubnetPlugin.pm | 11 +
> src/PVE/Network/SDN/Vnets.pm | 2 +-
> src/PVE/Network/SDN/Zones.pm | 29 +-
> src/PVE/Network/SDN/Zones/EvpnPlugin.pm | 40 +-
> src/PVE/Network/SDN/Zones/FaucetPlugin.pm | 1 +
> src/PVE/Network/SDN/Zones/QinQPlugin.pm | 7 +
> src/PVE/Network/SDN/Zones/SimplePlugin.pm | 2 +-
> src/PVE/Network/SDN/Zones/VlanPlugin.pm | 7 +
> src/PVE/Network/SDN/Zones/VxlanPlugin.pm | 31 +-
> src/test/run_test_vnets_blackbox.pl | 1017 ++++++++++++++++-
> .../underlay_mtu/expected_controller_config | 44 +
> .../evpn/underlay_mtu/expected_sdn_interfaces | 42 +
> src/test/zones/evpn/underlay_mtu/interfaces | 8 +
> src/test/zones/evpn/underlay_mtu/sdn_config | 26 +
> .../underlay_mtu/expected_sdn_interfaces | 16 +
> src/test/zones/vxlan/underlay_mtu/interfaces | 8 +
> src/test/zones/vxlan/underlay_mtu/sdn_config | 11 +
> 24 files changed, 1770 insertions(+), 37 deletions(-)
> create mode 100755 debian/libpve-network-perl.prerm
> create mode 100644 src/PVE/Network/SDN/Dhcp/Ebpf.pm
> create mode 100644 src/test/zones/evpn/underlay_mtu/expected_controller_config
> create mode 100644 src/test/zones/evpn/underlay_mtu/expected_sdn_interfaces
> create mode 100644 src/test/zones/evpn/underlay_mtu/interfaces
> create mode 100644 src/test/zones/evpn/underlay_mtu/sdn_config
> create mode 100644 src/test/zones/vxlan/underlay_mtu/expected_sdn_interfaces
> create mode 100644 src/test/zones/vxlan/underlay_mtu/interfaces
> create mode 100644 src/test/zones/vxlan/underlay_mtu/sdn_config
>
>
> qemu-server:
>
> Hannes Laimer (1):
> network: sdn: keep the DHCP backends current on guest NICs
>
> src/PVE/CLI/qm.pm | 4 ++--
> src/PVE/QemuServer.pm | 4 ++++
> src/PVE/QemuServer/Network.pm | 4 ++--
> src/test/hotplug/net-change-bridge.conf.expected | 3 ++-
> src/usr/pve-bridge | 8 +++++++-
> src/usr/pve-bridgedown | 4 ++--
> 6 files changed, 19 insertions(+), 8 deletions(-)
>
>
> pve-container:
>
> Hannes Laimer (1):
> net: report NIC plugs and removals to the SDN DHCP backends
>
> src/PVE/LXC.pm | 13 +++++++++++--
> src/PVE/LXC/Config.pm | 3 ++-
> src/lxc-pve-poststop-hook | 6 +++---
> 3 files changed, 16 insertions(+), 6 deletions(-)
>
>
> pve-manager:
>
> Hannes Laimer (2):
> ui: sdn: add zone DHCP backend selector and subnet DHCP options
> sdn: bring up the DHCP backends at boot before the guests start
>
> bin/pve-sdn-commit | 4 ++++
> services/pve-sdn-commit.service | 1 +
> www/manager6/sdn/SubnetEdit.js | 23 +++++++++++++++++++++++
> www/manager6/sdn/zones/Base.js | 17 +++++++++++++++++
> www/manager6/sdn/zones/SimpleEdit.js | 11 -----------
> 5 files changed, 45 insertions(+), 11 deletions(-)
>
>
> proxmox-ve-rs:
>
> Hannes Laimer (1):
> ve-config: sdn: add the ebpf dhcp backend
>
> proxmox-ve-config/src/sdn/config.rs | 3 +++
> 1 file changed, 3 insertions(+)
>
>
> pve-docs:
>
> Hannes Laimer (2):
> sdn: zones: document the MTU taken from the underlay interface
> sdn: dhcp: add eBPF backend section
>
> pvesdn.adoc | 142 +++++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 108 insertions(+), 34 deletions(-)
>
>
> Summary over all repositories:
> 58 files changed, 4822 insertions(+), 101 deletions(-)
>
prev parent reply other threads:[~2026-11-12 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 10:02 [PATCH container/docs/manager/network/proxmox{,-perl-rs,-ve-rs}/qemu-server v6 00/17] sdn: implement DHCP for all zones using eBPF Hannes Laimer
2026-11-05 10:03 ` [PATCH proxmox v6 01/17] network-types: mac address: add an accessor for the bytes Hannes Laimer
2026-11-05 10:03 ` [PATCH proxmox v6 02/17] ebpf: dhcp: add the per-tap DHCPv4 responder program Hannes Laimer
2026-11-05 10:03 ` [PATCH proxmox v6 03/17] ebpf: dhcp: add the subsystem that loads the responder and keeps its records Hannes Laimer
2026-11-05 10:03 ` [PATCH proxmox-perl-rs v6 04/17] pve-rs: sdn: add bindings for the eBPF DHCP responder Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 05/17] sdn: zones: take the VXLAN and EVPN MTU from the underlay interface Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 06/17] sdn: dhcp: make the lease time configurable per subnet Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 07/17] sdn: dhcp: require a backend only if a zone on this node uses it Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 08/17] sdn: dhcp: add an eBPF backend answering on each guest interface Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 09/17] sdn: zones: report interface plugs and unplugs to the DHCP backends Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-network v6 10/17] sdn: zones: allow the ebpf DHCP backend on every zone type Hannes Laimer
2026-11-05 10:03 ` [PATCH qemu-server v6 11/17] network: sdn: keep the DHCP backends current on guest NICs Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-container v6 12/17] net: report NIC plugs and removals to the SDN DHCP backends Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-manager v6 13/17] ui: sdn: add zone DHCP backend selector and subnet DHCP options Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-manager v6 14/17] sdn: bring up the DHCP backends at boot before the guests start Hannes Laimer
2026-11-05 10:03 ` [PATCH proxmox-ve-rs v6 15/17] ve-config: sdn: add the ebpf dhcp backend Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-docs v6 16/17] sdn: zones: document the MTU taken from the underlay interface Hannes Laimer
2026-11-05 10:03 ` [PATCH pve-docs v6 17/17] sdn: dhcp: add eBPF backend section Hannes Laimer
2026-11-12 12:45 ` Hannes Laimer [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=62562a47-0279-405c-9608-582bc85acb96@proxmox.com \
--to=h.laimer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox