all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager/network 0/3] add IPv6 SLAAC for vnets in evpn zones
Date: Mon, 19 Jan 2026 08:01:24 +0100	[thread overview]
Message-ID: <e7ddbee2-ae2d-49ee-833b-b67b89f90319@proxmox.com> (raw)
In-Reply-To: <20260114145257.47587-1-h.laimer@proxmox.com>

When we allow setting a ND prefix for the RAs to advertise, we could end
up with one that does not match the configured gateway one on a subnet.
We shouldn't allow setting the prefix explicitly, but just "enable
SLAAC" on a configured IPv6 subnet.

I'll send a v2 for this, sorry for the noise.

On 1/14/26 15:52, Hannes Laimer wrote:
> 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(-)
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2026-01-19  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 14:52 Hannes Laimer
2026-01-14 14:52 ` [pve-devel] [PATCH pve-network 1/2] evpn: add ipv6 slaac support for vnets in an evpn zone Hannes Laimer
2026-01-14 14:52 ` [pve-devel] [PATCH pve-network 2/2] evpn: add test for vnets with a `ipv6-nd-prefix` set Hannes Laimer
2026-01-14 14:52 ` [pve-devel] [PATCH pve-manager 1/1] ui: sdn: add `ipv6-nd-prefix` field to vnet form Hannes Laimer
2026-01-19  7:01 ` 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=e7ddbee2-ae2d-49ee-833b-b67b89f90319@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal