From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] sdn: fabrics: remove duplicate paragraph in OSPF section
Date: Thu, 17 Jul 2025 11:12:24 +0200 [thread overview]
Message-ID: <20250717091224.1856-1-h.laimer@proxmox.com> (raw)
Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
pvesdn.adoc | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 3d793cb..4ed8e88 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -710,14 +710,10 @@ Configuration options:
On the Fabric
^^^^^^^^^^^^^
-Area:: This specifies the OSPF area identifier, which can be either a 32-bit
-signed integer or an IP address. Areas are a way to organize and structure OSPF
-networks hierarchically, with Area 0 (or 0.0.0.0) serving as the backbone area.
-
IPv4 Prefix:: IPv4 CIDR network range (e.g., 192.0.2.0/24) used to
verify that all router-IDs in the fabric are contained within this prefix.
-Area:: This specifies the OSPF area identifier, which can be either an 32-bit
+Area:: This specifies the OSPF area identifier, which can be either a 32-bit
signed integer or an IP address. Areas are a way to organize and structure OSPF
networks hierarchically, with Area 0 (or 0.0.0.0) serving as the backbone area.
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-17 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 9:12 Hannes Laimer [this message]
2025-07-24 11:04 ` [pve-devel] applied: " 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=20250717091224.1856-1-h.laimer@proxmox.com \
--to=h.laimer@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.