From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: applied: [PATCH ifupdown2 v2 0/2] ifupdown2 vxlan fixes
Date: Tue, 10 Nov 2026 21:43:16 +0100 [thread overview]
Message-ID: <179434327682.2631194.8570797019873501520.b4-ty@b4> (raw)
In-Reply-To: <20261106-fix_8299_only-v2-0-19b90284c405@proxmox.com>
On Fri, 06 Nov 2026 18:15:49 +0100, Gabriel Goller wrote:
> This series avoids unnecessary vxlan and vlan device recreation on reload
> and fixes IPv6 peer detection in the vxlan fdb. More details are in the
> commit messages.
Applied, thanks!
[1/2] fix #8299: only recreate vxlan and vlan devices on reload if required
commit: 3ef577af22b5882051bb638e556007cc93d83a68
[2/2] vxlan: match IPv6 peers when reading the fdb
commit: 49b06baac7ba5af810977219ca5e06831a213e62
I folded two fix-ups into the second one:
- Skip the vxlan-svcnodeip6 or vxlan-mcastgrp6 address, which the kernel
also lists as an all-zero fdb entry, so that it is not deleted together
with removed remotes.
- Normalize the configured remotes before comparing them with the fdb,
so that a remote written as, e.g., 2001:DB8:0::3 matches its fdb entry
2001:db8::3 instead of being deleted and re-added whenever the remotes
change.
prev parent reply other threads:[~2026-11-10 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:15 [PATCH ifupdown2 v2 0/2] ifupdown2 vxlan fixes Gabriel Goller
2026-11-06 17:15 ` [PATCH ifupdown2 v2 1/2] fix #8299: only recreate vxlan and vlan devices on reload if required Gabriel Goller
2026-11-06 17:15 ` [PATCH ifupdown2 v2 2/2] vxlan: match IPv6 peers when reading the fdb Gabriel Goller
2026-11-06 17:18 ` Gabriel Goller
2026-11-10 10:44 ` [PATCH ifupdown2 v2 0/2] ifupdown2 vxlan fixes Lukas Sichert
2026-11-10 20:43 ` Thomas Lamprecht [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=179434327682.2631194.8570797019873501520.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@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