From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 1/2] sdn: route maps: mention implicit deny default explicitly
Date: Wed, 13 May 2026 18:20:10 +0200 [thread overview]
Message-ID: <20260513162013.456890-2-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20260513162013.456890-1-s.hanreich@proxmox.com>
While mentioned in the examples, it is good to clarify this in the
route map section as well.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
pvesdn.adoc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 6bb4993..9a3b6b8 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -841,7 +841,8 @@ A route map is an ordered list of entries that match incoming or outgoing
routes against criteria, optionally modify attributes such as the metric or
local preference, and either `permit` (forward the route, possibly modified) or
`deny` (drop the route). FRR evaluates entries in order; the first match
-controls the action.
+controls the action. Every route map implicitly has an otherwise empty `deny` as
+its last entry, denying all routes that did not match an entry explicitly.
Route maps are managed under `Datacenter -> SDN -> Route Maps`. Each entry has
the following properties:
--
2.47.3
next prev parent reply other threads:[~2026-05-13 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:20 [PATCH docs 0/2] Improve route map documentation Stefan Hanreich
2026-05-13 16:20 ` Stefan Hanreich [this message]
2026-05-13 16:20 ` [PATCH pve-docs 2/2] sdn: route map: delete note about creating an empty deny entry Stefan Hanreich
2026-05-13 16:48 ` applied: [PATCH docs 0/2] Improve route map documentation 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=20260513162013.456890-2-s.hanreich@proxmox.com \
--to=s.hanreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox