From: Gabriel Goller <g.goller@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-ve-rs v2 1/7] sdn: fabric: add BGP protocol support
Date: Thu, 16 Apr 2026 11:17:47 +0200 [thread overview]
Message-ID: <whqitzk535c27tbpcjppnenwrgqynszaeaqmg76dqoutxubtzk@lfqxyzft4nbv> (raw)
In-Reply-To: <20260415111134.124720-2-h.laimer@proxmox.com>
On 15.04.2026 13:11, Hannes Laimer wrote:
> From: Stefan Hanreich <s.hanreich@proxmox.com>
>
> Add BGP as a fabric protocol for eBGP unnumbered underlays. Each node
> has a mandatory, globally unique ASN for interface-based eBGP peering.
>
> Unlike OSPF and OpenFabric, BGP does not have its own FRR daemon -
This is a bit wrong, BGP has its own frr daemon, maybe rewrite this as "the bgp
router is not exclusive to the bgp fabric"?
> the fabric config needs to coexist with EVPN in a single 'router bgp'
> block. To handle this, the fabric merges into an existing router
> rather than replacing it, using local-as to present the per-node ASN
> to underlay peers when the router already runs under the EVPN ASN.
>
> For IPv6-only nodes, the BGP router-id is derived from the IPv6
> address using FNV-1a, since router-id must be a 32-bit value.
Hmm this is a bit weird since the generated address is not really reachable
right?
How do we handle this (frr bgp docs)?:
To derive system-IP and anycast-IP, the default BGP instance’s router-id is
used as system-IP and the VxLAN interface’s local tunnel IP as the anycast-IP.
Would it be stupid to select a ipv4 address, set it on the lo interface and then
just use update-source and set the ipv6 address?
> Co-authored-by: Hannes Laimer <h.laimer@proxmox.com>
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
Maybe a few more tests with other existing fabrics, e.g. ospf and openfabric?
These are quite easy to add, so adding a few more won't hurt.
next prev parent reply other threads:[~2026-04-16 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:11 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v2 0/7] sdn: add BGP fabric Hannes Laimer
2026-04-15 11:11 ` [PATCH proxmox-ve-rs v2 1/7] sdn: fabric: add BGP protocol support Hannes Laimer
2026-04-16 9:17 ` Gabriel Goller [this message]
2026-04-16 12:46 ` Hannes Laimer
2026-04-15 11:11 ` [PATCH proxmox-perl-rs v2 2/7] sdn: fabrics: add BGP config generation Hannes Laimer
2026-04-15 11:11 ` [PATCH proxmox-perl-rs v2 3/7] sdn: fabrics: add BGP status endpoints Hannes Laimer
2026-04-15 11:11 ` [PATCH pve-network v2 4/7] sdn: fabrics: register bgp as a fabric protocol type Hannes Laimer
2026-04-15 11:11 ` [PATCH pve-network v2 5/7] test: evpn: add integration test for EVPN over BGP fabric Hannes Laimer
2026-04-15 11:11 ` [PATCH pve-manager v2 6/7] ui: sdn: add BGP fabric support Hannes Laimer
2026-04-15 11:11 ` [PATCH pve-docs v2 7/7] sdn: add bgp fabric section Hannes Laimer
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=whqitzk535c27tbpcjppnenwrgqynszaeaqmg76dqoutxubtzk@lfqxyzft4nbv \
--to=g.goller@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox