From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Lukas Sichert" <l.sichert@proxmox.com>,
"Hannes Laimer" <h.laimer@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones
Date: Fri, 30 Oct 2026 17:30:32 +0100 [thread overview]
Message-ID: <DMIBDUSLZ9A8.1RH0JLAB5UKDL@proxmox.com> (raw)
In-Reply-To: <DMI9MCSBGFCY.2KMP9KR1E4JJ9@proxmox.com>
On 2026-10-30 16:07, Lukas Sichert <l.sichert@proxmox.com> wrote:
> On 2026-10-29 16:41, Hannes Laimer <h.laimer@proxmox.com> wrote:
>
>> This series adds IPv6 Router Advertisement / SLAAC support to EVPN
>> zones.
>
> I have only tested this very briefly on a three node cluster with an
> existing IPv6 EVPN zone. After enabling 'Send Router Advertisements' on
> a vnet called 'evpnet' and applying, then disabling and applying again,
> the task exits with a warning. Going by the tasklog it seems to be
> trying to remove the interface from frr even though it is still up:
As discussed off list this is not actually harmful, just a bit noisy. FRR
refuses to delete an interface that is still up, so any time a whole
'interface <name>' block disappears from frr.conf, frr-reload.py fails
the same way. Removing an interface from a fabric triggers the same task
warning. The failed reload falls back to restarting frr, which leaves the
configuration in the correct state, and the next Apply is clean. So this
is not something this series needs to fix. Sorry for the noise.
prev parent reply other threads:[~2026-10-30 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 15:41 [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-perl-rs v5 1/9] pve-rs: sdn: add IPv6 RA builder binding Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-ve-rs v5 2/9] frr: add IPv6 router advertisement support Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-ve-rs v5 3/9] ve-config: sdn: add IPv6 router advertisement settings Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-manager v5 4/9] ui: sdn: add IPv6 RA / SLAAC support Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 5/9] sdn: evpn: derive IP version from CIDR for gateway-less subnets Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 6/9] sdn: evpn: accept untracked IPv6 neighbor advertisements Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 7/9] sdn: evpn: add IPv6 RA / SLAAC support Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 8/9] api: vnets: include the zone type in the vnet list Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-docs v5 9/9] sdn: add IPv6 RA / SLAAC section Hannes Laimer
2026-10-30 15:07 ` [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones Lukas Sichert
2026-10-30 16:30 ` Lukas Sichert [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=DMIBDUSLZ9A8.1RH0JLAB5UKDL@proxmox.com \
--to=l.sichert@proxmox.com \
--cc=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