From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: applied: [PATCH manager/network/proxmox-ve-rs v2 0/3] Expose OSPF Network-Type option
Date: Fri, 15 May 2026 07:00:27 +0200 [thread overview]
Message-ID: <177882102764.374183.18387370701578197444.b4-ty@b4> (raw)
In-Reply-To: <20260505091342.106949-1-g.goller@proxmox.com>
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: expose network-type interface property
commit: 5e559896a8853b8b1145b08d2ce1fb99e3810f6f
next prev parent reply other threads:[~2026-05-15 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 9:13 [PATCH manager/network/proxmox-ve-rs v2 0/3] Expose OSPF Network-Type option Gabriel Goller
2026-05-05 9:13 ` [PATCH proxmox-ve-rs v2 1/3] fabrics: ospf: expose network-type interface property Gabriel Goller
2026-05-05 9:13 ` [PATCH pve-network v2 2/3] fabrics: add ospf network_type property to interfaces Gabriel Goller
2026-05-05 9:13 ` [PATCH pve-manager v2 3/3] fabrics: ospf: add network-type property in interface panel Gabriel Goller
2026-05-15 5:00 ` Thomas Lamprecht [this message]
2026-05-15 5:04 ` applied: [PATCH manager/network/proxmox-ve-rs v2 0/3] Expose OSPF Network-Type option Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177882102764.374183.18387370701578197444.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.