From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 692501FF137 for ; Tue, 31 Mar 2026 13:44:52 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D135019976; Tue, 31 Mar 2026 13:45:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rchrist.io; s=default; t=1774957507; bh=C68xUXCikQvSxdGaKVdADQ6a753b/Vq7ui17BUmbKEM=; h=Date:Cc:Subject:From:To:References:In-Reply-To:From; b=UbdRdCfsFtivteWzJs/OlQlXjBRO1rZKSQjKPzrbEZpT/gPs4StgUoXRUnZ2us57E PS8vCkHrfaK8r+Wa9igqDUDb42wS+0A/jIteR5OzWzl+4P/tJWIfl4dWJrqFVCPZI0 KG6m8aZDoG+bJDg6tWom1yExyLsRCM1sdVhF1UHFJKUhjWKymeC3oaI1ojok5Jq/aI qoQnDf6k5tZDNNm7E0YybqCEcPSHNQhr87UJEXcbGJYGPxFg0kgyW7yphbYZGGeaXe n52fNV9i7cEGgJPlCa/AKWzu1FVJ34NySSWcl7DPldfpuv/2PIeFPvmDXGfrPbhIT6 +8z2fTfEdC/vw== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 31 Mar 2026 13:45:00 +0200 Message-Id: Subject: Re: [PATCH ifupdown2 4/4] bridge: Fix multiple Single VXLAN Devices in bridge not having tunnel_info applied on first run From: "Robin Christ" To: "Gabriel Goller" , "Robin Christ" X-Mailer: aerc 0.20.1-270-g2fb08ac189a1 References: <20260330213921.533853-1-robin@rchrist.io> <20260330213921.533853-5-robin@rchrist.io> In-Reply-To: X-Virus-Scanned: ClamAV using ClamSMTP X-SPAM-LEVEL: Spam detection results: 0 AWL -1.490 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_MISSING 0.1 Missing DMARC policy RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_MSPIKE_H3 -0.01 Good reputation (+3) RCVD_IN_MSPIKE_WL -0.01 Mailspike good senders RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: SSBK2JEA2UHASO3EQ3ZEJ4NYURZNPOS7 X-Message-ID-Hash: SSBK2JEA2UHASO3EQ3ZEJ4NYURZNPOS7 X-MailFrom: robin@rchrist.io 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 CC: pve-devel@lists.proxmox.com, Robin Christ X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue Mar 31, 2026 at 10:18 AM CEST, Gabriel Goller wrote: = = =20 > Thanks for these patches! = = =20 > If you haven't already, please sign the contribution = = =20 > agreement and send it to office@proxmox.com = = =20 > (https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_an= d_Copyright). = =20 = = =20 On it, probably gonna send it tomorrow. = = =20 = = =20 > The dry-run patches before look good, maybe @Christoph can have a look at= them as well. = =20 = = =20 I noticed that in my last patch, there is a little typo in debian/patches/s= eries as I renamed the patch file. = =20 Should I post a new patch or can that be fixed on merge? = = =20 = = =20 > About this one though: what is the use-case? we don't use SVDs and so the= = =20 > tunnel_info property is also not used AFAIK? = = =20 = = =20 Not yet... ;) We (Partimus) are currently rebuilding our entire network, an= d we use a lot of EVPN with Proxmox. = =20 We're probably building one of the most extreme EVPN setups you'll ever fin= d in the wild right now, but all based on Proxmox. = =20 We completely circumvent the existing Proxmox SDN though, as it by far does= n't fit our requirements. = =20 = = =20 TL;DR our use case for SVDs, and multiple SVDs in a single bridge: Traffic = Steering. = =20 I will drop you some details via direct e-mail. = = =20 = = =20 As it seems like ifupdown2 upstream development has effectively been halted= , Proxmox seemed like the best way = =20 to file the fixes.