From: "DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
"pve-devel-bounces@lists.proxmox.com"
<pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-network 1/5] controllers: fix maximum value for ASN
Date: Tue, 11 Mar 2025 10:50:50 +0000 [thread overview]
Message-ID: <mailman.966.1741691214.293.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.927.1741672428.293.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 12796 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "pve-devel-bounces@lists.proxmox.com" <pve-devel-bounces@lists.proxmox.com>, "m@mpgn.dev" <m@mpgn.dev>
Subject: Re: [pve-devel] [PATCH pve-network 1/5] controllers: fix maximum value for ASN
Date: Tue, 11 Mar 2025 10:50:50 +0000
Message-ID: <ed3068f4374e35ef9187013e2e581369e2aec1eb.camel@groupe-cyllene.com>
>>According to my testing, when using the `autort` for RT auto-
>>derivation
>>(from the frr patch) causes issues because it doesn't work with 32
>>bits
>>ASNs, effectively calling the fallback to restarting frr to apply the
>>config (which ignores the autort instruction).
yes, this is a limitation because route-target AS:VNI is 48bits,
and VNI can go up to 32bits , so AS can't be more than 16bits.
I don't known if it's working if you only use small VNI
I think they are the RFC 5668 to handle it, but I never had time to
dig it
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-11 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:01 [pve-devel] [PATCH network 0/5] Improve documentation for SDN API endpoints used by PDM Stefan Hanreich
2025-02-28 14:01 ` [pve-devel] [PATCH pve-network 1/5] controllers: fix maximum value for ASN Stefan Hanreich
2025-03-10 15:29 ` Shannon Sterz
2025-03-11 5:53 ` Matthieu Pignolet via pve-devel
2025-03-11 10:50 ` DERUMIER, Alexandre via pve-devel [this message]
2025-02-28 14:01 ` [pve-devel] [PATCH pve-network 2/5] api: add state standard option Stefan Hanreich
2025-02-28 14:01 ` [pve-devel] [PATCH pve-network 3/5] api: controllers: update schema of endpoints Stefan Hanreich
2025-02-28 14:01 ` [pve-devel] [PATCH pve-network 4/5] api: vnets: " Stefan Hanreich
2025-02-28 14:01 ` [pve-devel] [PATCH pve-network 5/5] api: zones: " Stefan Hanreich
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=mailman.966.1741691214.293.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel-bounces@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