From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-network 0/1] controllers: evpn: fix multiple exit-nodes with route-map filtering
Date: Wed, 20 Apr 2022 16:19:29 +0200 [thread overview]
Message-ID: <20220420141930.1626073-1-aderumier@odiso.com> (raw)
2 forums users have reported problems when multiple evpn exit-nodes are defined.
This was because of a loop between default gw exchanged between the exit-nodes.
This patch add a filtering of incoming default routes on the exit-nodes with a new route-map
Alexandre Derumier (1):
controllers: evpn: fix multiple exit-nodes with route-map filtering
PVE/Network/SDN/Controllers/BgpPlugin.pm | 5 ++--
PVE/Network/SDN/Controllers/EvpnPlugin.pm | 23 +++++++++++++++----
.../expected_controller_config | 3 +++
.../expected_controller_config | 3 +++
.../evpn/ebgp/expected_controller_config | 3 +++
.../ebgp_loopback/expected_controller_config | 3 +++
.../evpn/exitnode/expected_controller_config | 6 +++++
.../expected_controller_config | 6 +++++
.../expected_controller_config | 3 +++
.../exitnode_snat/expected_controller_config | 6 +++++
.../evpn/ipv4/expected_controller_config | 3 +++
.../evpn/ipv4ipv6/expected_controller_config | 3 +++
.../expected_controller_config | 3 +++
.../evpn/ipv6/expected_controller_config | 3 +++
.../expected_controller_config | 3 +++
.../evpn/rt_import/expected_controller_config | 3 +++
16 files changed, 72 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-20 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:19 Alexandre Derumier [this message]
2022-04-20 14:19 ` [pve-devel] [PATCH pve-network 1/1] " Alexandre Derumier
2022-04-27 8:34 ` [pve-devel] applied: " 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=20220420141930.1626073-1-aderumier@odiso.com \
--to=aderumier@odiso.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.