From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id E3E761FF13F for ; Wed, 14 Jan 2026 15:53:28 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E2C4615B86; Wed, 14 Jan 2026 15:53:32 +0100 (CET) From: Hannes Laimer To: pve-devel@lists.proxmox.com Date: Wed, 14 Jan 2026 15:52:54 +0100 Message-ID: <20260114145257.47587-1-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1768402333303 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.057 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH manager/network 0/3] add IPv6 SLAAC for vnets in evpn zones X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" FRR natively supports sending RAs, if configured to do so, dnsmasq also doesn't seem to correctly send RAs in a VRF context. Both DHCPv4 and v6 worked fine when running on a VNet, but RAs just wouldn't be send correctly. From a quick look it may have to the with dnsmasq not using the link-local address of the interface, or not sending it if the interface also has another address attached. [1][2] I did try building it myself with some changes, but could not get the RA packets to "hit the wire", they never showed up in tcpdump. So either they were not sent or the kernel dropped them cause they didn't have a ll source address. Regardless, these are the two reasons why I went with using FRR directly rather than using dnsmasq like we aleardy do for DHCPv4. This series adds a `ipv6-nd-prefix`-option for vnets that is than used by client on the vnet to perform SLAAC. Without a prefix specified, SLAAC is not enabled. [1] https://thekelleys.org.uk/gitweb1/?p=dnsmasq.git;a=blob;f=src/radv.c;h=aaf6b71e27ba392d7517c68fa90f251eccbf4641;hb=d8f66f4fda02ca50616f428d9c161c8ca1a0cb70#l308 [2] https://thekelleys.org.uk/gitweb1/?p=dnsmasq.git;a=blob;f=src/dhcp6.c;h=482caf7dd492849f5a454316d86e759677c0072a;hb=d8f66f4fda02ca50616f428d9c161c8ca1a0cb70#l138 pve-network: Hannes Laimer (2): evpn: add ipv6 slaac support for vnets in an evpn zone evpn: add test for vnets with a `ipv6-nd-prefix` set src/PVE/API2/Network/SDN/Vnets.pm | 7 +++ src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 15 ++++++ src/PVE/Network/SDN/VnetPlugin.pm | 8 +++ .../expected_controller_config | 49 +++++++++++++++++++ .../ipv6_slaacprefix/expected_sdn_interfaces | 42 ++++++++++++++++ .../zones/evpn/ipv6_slaacprefix/interfaces | 7 +++ .../zones/evpn/ipv6_slaacprefix/sdn_config | 39 +++++++++++++++ 7 files changed, 167 insertions(+) create mode 100644 src/test/zones/evpn/ipv6_slaacprefix/expected_controller_config create mode 100644 src/test/zones/evpn/ipv6_slaacprefix/expected_sdn_interfaces create mode 100644 src/test/zones/evpn/ipv6_slaacprefix/interfaces create mode 100644 src/test/zones/evpn/ipv6_slaacprefix/sdn_config pve-manager: Hannes Laimer (1): ui: sdn: add `ipv6-nd-prefix` field to vnet form www/manager6/sdn/VnetEdit.js | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) Summary over all repositories: 8 files changed, 188 insertions(+), 0 deletions(-) -- Generated by git-murpp 0.8.1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel