From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ifupdown2 v2 0/2] ifupdown2 vxlan fixes
Date: Fri, 06 Nov 2026 18:15:49 +0100 [thread overview]
Message-ID: <20261106-fix_8299_only-v2-0-19b90284c405@proxmox.com> (raw)
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.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
Wasn't sure if I should leave the old patch and make a new one
overriding it or if I should delete it. Went for the second version, let
me know if I should do it differently.
---
Changes in v2:
- vxlan: always re-add missing fdb entries for configured remotes, not
only when the saved config changed; only delete on remote changes
(thanks @Daniel Herzig)
- new patch: match IPv6 peers when reading the vxlan fdb
- Link to v1: https://lore.proxmox.com/all/20261106-fix_8299_only-v1-1-a7d760fff147@proxmox.com
---
Gabriel Goller (2):
fix #8299: only recreate vxlan and vlan devices on reload if required
vxlan: match IPv6 peers when reading the fdb
...wn-up-vxlan-vlan-interfaces-when-ifreload.patch | 39 ---
...ly-recreate-vxlan-and-vlan-devices-if-req.patch | 294 +++++++++++++++++++++
...lan-match-IPv6-peers-when-reading-the-fdb.patch | 27 ++
debian/patches/series | 3 +-
4 files changed, 323 insertions(+), 40 deletions(-)
---
base-commit: 705d9a203ae3a8a896b4fb03217701c65b10ef21
change-id: 20261106-fix_8299_only-86419dd42acd
Best regards,
--
Gabriel Goller <g.goller@proxmox.com>
next reply other threads:[~2026-11-06 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:15 Gabriel Goller [this message]
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
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=20261106-fix_8299_only-v2-0-19b90284c405@proxmox.com \
--to=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 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.