From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40])
	by lore.proxmox.com (Postfix) with ESMTPS id AC7AF1FF0B4
	for <inbox@lore.proxmox.com>; Tue, 10 Nov 2026 21:48:15 +0100 (CET)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 7755E21611;
	Tue, 10 Nov 2026 21:48:12 +0100 (CET)
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
Message-ID: <179434327682.2631194.8570797019873501520.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20261106-fix_8299_only-v2-0-19b90284c405@proxmox.com>
References: <20261106-fix_8299_only-v2-0-19b90284c405@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1794343687752
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.266 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: 4JM5VZMLUU6MBNGVMEP4M6SZ56AZU2CA
X-Message-ID-Hash: 4JM5VZMLUU6MBNGVMEP4M6SZ56AZU2CA
X-MailFrom: t.lamprecht@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.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.