From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 1C0D81FF0F5 for ; Mon, 02 Nov 2026 23:52:52 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B60D321817; Mon, 02 Nov 2026 23:52:38 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH pve-network] sdn: zones: vxlan: set the local tunnel address explicitly Date: Mon, 2 Nov 2026 23:51:55 +0100 Message-ID: <179365989922.2007812.4485405588835907272.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260925134050.754528-1-h.laimer@proxmox.com> References: <20260925134050.754528-1-h.laimer@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: 1793659954533 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.351 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: ENFUXWYID4DFYUVNG74DSE2KRYCMAP73 X-Message-ID-Hash: ENFUXWYID4DFYUVNG74DSE2KRYCMAP73 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 List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 25 Sep 2026 15:40:50 +0200, Hannes Laimer wrote: > The plugin already determines which peer address is the node's own, > but only uses it to leave the node out of the remote list and never > writes it as vxlan-local-tunnelip. ifupdown2 applies the first local > tunnel address it processes in a run to every vxlan interface without > one, so a VXLAN zone next to an EVPN zone inherits the EVPN zone's > address, at creation and on reload as an in-place change of the live > device. With both zones on one underlay the two addresses are the > same. With separate underlays the zone's VTEP address lands on the > EVPN underlay, FRR advertises the VNI with it and installs forwarding > entries toward the peers there, and the zone's traffic moves onto the > EVPN underlay. > > [...] Applied, thanks! [1/1] sdn: zones: vxlan: set the local tunnel address explicitly commit: 3d14daeeb5da32ca82eb3757bbfa0a87b2ded719