From: Gabriel Goller <g.goller@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs/manager/network/proxmox-ve-rs v2 00/18] Extend EVPN controller functionality
Date: Fri, 8 May 2026 15:33:07 +0200 [thread overview]
Message-ID: <4idehi5z4brczmlpx4azwhfvgbypqhpyrjdqkwlpjtn77q7qb2@7m7iipqlvibg> (raw)
In-Reply-To: <20260504162501.425135-1-s.hanreich@proxmox.com>
The "update-source" generation here is a bit weird. When having bgp controllers
+ multiple evpn controllers, and have "loopback interface" set on the bgp
controller, we set `update-source <interface>` on both neighbor groups (both
evpn controllers). This doesn't work if your two evpn controllers have peers
that are in different subnets, because then the wrong source address will be
chosen.
We can fix this by setting the `update-source` property only when the 'Legacy'
mode on the evpn controller is on.
AFAICS we automatically select the correct source address anyway as the source
should be in the route inserted by the underlay.
prev parent reply other threads:[~2026-05-08 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 16:24 [PATCH docs/manager/network/proxmox-ve-rs v2 00/18] Extend EVPN controller functionality Stefan Hanreich
2026-05-04 16:24 ` [PATCH proxmox-ve-rs v2 01/18] frr: add local-as setting Stefan Hanreich
2026-05-04 16:24 ` [PATCH proxmox-ve-rs v2 02/18] frr: add support for extcommunity lists Stefan Hanreich
2026-05-04 16:24 ` [PATCH proxmox-ve-rs v2 03/18] frr-templates: render local-as setting Stefan Hanreich
2026-05-04 16:24 ` [PATCH proxmox-ve-rs v2 04/18] frr-templates: render community lists in templates Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 05/18] evpn controller: make nodes configurable Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 06/18] evpn controller: allow multiple evpn controllers in a cluster Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 07/18] evpn controller: add bgp-mode setting Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 08/18] evpn zone: add secondary-controllers and rt filtering Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 09/18] evpn controller: add ebgp-multihop setting Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 10/18] test: evpn: add test for ibgp + ebgp evpn controller Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 11/18] test: evpn: add legacy test Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 12/18] tests: add rt_import test case when using multiple evpn controllers Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 13/18] " Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 14/18] tests: evpn: force ibgp over ebgp bgp controller with ebgp wan session Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-network v2 15/18] tests: test route filtering mechanism with multiple zones/controllers Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-manager v2 16/18] sdn: evpn: zone: controller: add new advanced fields Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-docs v2 17/18] sdn: evpn: document new zone / controller options Stefan Hanreich
2026-05-04 16:24 ` [PATCH pve-docs v2 18/18] sdn: fix typo in bgp controller Stefan Hanreich
2026-05-08 13:33 ` Gabriel Goller [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=4idehi5z4brczmlpx4azwhfvgbypqhpyrjdqkwlpjtn77q7qb2@7m7iipqlvibg \
--to=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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