public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Cole Hughes <c.hughes@proxmox.com>
To: pve-devel@lists.proxmox.com, c.hughes@proxmox.com
Subject: [PATCH network 3/3] sdn: removing ASN number
Date: Fri, 28 Aug 2026 14:24:05 -0400	[thread overview]
Message-ID: <20260828182412.47042-4-c.hughes@proxmox.com> (raw)
In-Reply-To: <20260828182412.47042-1-c.hughes@proxmox.com>

ASN is the acronym for Autonomous System Number. "ASN number" is redundant.

Signed-off-by: Cole Hughes <c.hughes@proxmox.com>
---
 src/PVE/Network/SDN/Controllers/Plugin.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/PVE/Network/SDN/Controllers/Plugin.pm b/src/PVE/Network/SDN/Controllers/Plugin.pm
index 6da3eec..6d6b974 100644
--- a/src/PVE/Network/SDN/Controllers/Plugin.pm
+++ b/src/PVE/Network/SDN/Controllers/Plugin.pm
@@ -159,8 +159,8 @@ needs to always use the EVPN ASN in its router definition to ensure correct
 generation for Route Targets (if not using the autort patch).
 
 The FRR config generation logic utilizes the local-as directive for specifying
-alternate ASN numbers. Since local-as is only applicable for eBGP sessions, the
-internal ASN number always needs to be used for the router definition. So if
+alternate ASNs. Since local-as is only applicable for eBGP sessions, the
+internal ASN always needs to be used for the router definition. So if
 there are no EVPN controllers, but iBGP BGP sessions, utilize the ASN configured
 there.
 
-- 
Cole Hughes <c.hughes@proxmox.com>





      parent reply	other threads:[~2026-08-28 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 18:24 [PATCH docs/manager/network 0/3] remove ASN number Cole Hughes
2026-08-28 18:24 ` [PATCH docs 1/3] sdn: removing " Cole Hughes
2026-08-28 18:24 ` [PATCH manager 2/3] " Cole Hughes
2026-08-28 18:24 ` Cole Hughes [this message]

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=20260828182412.47042-4-c.hughes@proxmox.com \
    --to=c.hughes@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal