From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7F2F11FF14C for ; Fri, 15 May 2026 07:05:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 29F13BB26; Fri, 15 May 2026 07:05:37 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Gabriel Goller Subject: applied: [PATCH manager/network/proxmox-ve-rs v2 0/3] Expose OSPF Network-Type option Date: Fri, 15 May 2026 07:04:52 +0200 Message-ID: <177882145096.392510.6136917580213361245.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260505091342.106949-1-g.goller@proxmox.com> References: <20260505091342.106949-1-g.goller@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: 1778821496435 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: YBUUDTOLPFOFFMJJISXGRB7CWUNPAJOU X-Message-ID-Hash: YBUUDTOLPFOFFMJJISXGRB7CWUNPAJOU 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 Tue, 05 May 2026 11:13:35 +0200, Gabriel Goller wrote: > Previously the network-type option on OSPF interfaces was set to either > point-to-point or broadcast, depending on if an ip address was configured on > the interface. This is not enough, as some users want to have a switched > network (e.g. switch) between their nodes, which calls for the > point-to-multipoint network type. > > In order to uphold backwards-compatibility, make network-type an `Option`, > where `None` will be the "automatic" network-type selection we had before. > > [...] Applied, thanks! [1/1] fabrics: ospf: add network-type property in interface panel commit: 6e551f05438039c1d99bb8755a681a235f46b936