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 [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id 09AE31FF138
	for <inbox@lore.proxmox.com>; Mon, 20 Jul 2026 13:15:32 +0200 (CEST)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 4FA2E214F4;
	Mon, 20 Jul 2026 13:14:49 +0200 (CEST)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Lukas Sichert <l.sichert@proxmox.com>
Subject: applied: [PATCH network v2] snat: handle interface lookup failures
 gracefully
Date: Mon, 20 Jul 2026 13:13:48 +0200
Message-ID: <178454602798.2519483.9676563184724913593.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260601124228.77298-1-l.sichert@proxmox.com>
References: <20260601124228.77298-1-l.sichert@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: 1784546011898
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.227 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_LOW        -0.7 Sender listed at https://www.dnswl.org/,
 low 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: 2Q4UCXCGH7HFC6K26BZLKIQ5ZFTPKC36
X-Message-ID-Hash: 2Q4UCXCGH7HFC6K26BZLKIQ5ZFTPKC36
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 Mon, 01 Jun 2026 14:42:18 +0200, Lukas Sichert wrote:
> 'When an IPv6 subnet is created in a Simple or EVPN zone, the setup code
> runs 'ip route get 2001:4860:4860::8888' to determine the outgoing
> interface. If the host has no IPv6 address configured, this command
> fails and aborts the loop that iterates over the plugin's subnets. This
> means that the current and subsequent bridges required for the VNETs are
> not instantiated, even though they still appear in the GUI. Starting a
> VM connected to such a VNET then fails with: 'TASK ERROR: bridge
> '<vnet>' does not exist'.
> 
> [...]

Applied, thanks!

[1/1] snat: handle interface lookup failures gracefully
      commit: 304989ce75ceed5838c6cd7c481637e6d865e4d1