From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 69DDA1FF0AB for ; Wed, 07 Oct 2026 08:46:49 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 19C0A21320; Wed, 07 Oct 2026 08:46:48 +0200 (CEST) Message-ID: Date: Wed, 7 Oct 2026 08:46:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: SDN with BGP Fabric and IPv6 Only Underlay for VXLAN To: Tobias Fiebig , pve-devel@lists.proxmox.com References: <6a01449fcaee735648dbd8424d64c737a0428c9f.camel@internet.wien> <870c6dac7eb6683febc6bedaf679c500315216bd.camel@internet.wien> From: Hannes Laimer Content-Language: en-US In-Reply-To: <870c6dac7eb6683febc6bedaf679c500315216bd.camel@internet.wien> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1791355603056 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.511 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: S6CFPNBJEOJDH2PKP2WTV5AZTQCUCB6Q X-Message-ID-Hash: S6CFPNBJEOJDH2PKP2WTV5AZTQCUCB6Q X-MailFrom: h.laimer@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: Hey Tobias, yes, a patch for this specifically already exists [1], and with [2] also v6 fabrics should work. [1] https://lore.proxmox.com/pve-devel/20260925134050.754528-1-h.laimer@proxmox.com/ [2] https://lore.proxmox.com/pve-devel/20261007064553.164447-1-h.laimer@proxmox.com/T/#u On 2026-10-06 17:20, Tobias Fiebig wrote: > Moin, > > oh, and what I also noticed (discussed in the forums already ~4y ago, > see: > https://forum.proxmox.com/threads/sdn-wrong-automatic-vxlan-configuration-to-use-it-over-wiregaurd.106401/ > ) is that vxlan over IPv6 needs vxlan-local-tunnelip to be set to the > local tunnel; Currently using explicit peer definitions to make this > work, where there (at least) that is also being skipped in > /etc/network/interfaces.d/sdn. > > With best regards, > Tobias > > On Tue, 2026-10-06 at 16:46 +0200, Tobias Fiebig wrote: >> Moin, >> i am currently configuring a proxmox cluster that is supposed to be >> IPv6 only and attached to an RFC8950 based L3 fabric. >> >> While doing so, I noticed that VXLAN zones cannot be configured on an >> IPv6 only fabric; The reason for that is that >> >> /usr/share/perl5/PVE/Network/SDN/Zones/VxlanPlugin.pm >> >> Only checks for $current_node->{ip} in line 109. >> >> Subsequently, the peers and ifaceip are also set for v4 only. Adding >> logic for ip6 fixes this. >> >> (dropping this to the devel list, as it is not really a >> question/users >> point, and should be a straight forward fix.) >> >> With best regards, >> Tobias >