public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH pve-network 1/1] controllers: evpn: fix multiple exit-nodes with route-map filtering
Date: Wed, 27 Apr 2022 10:34:07 +0200	[thread overview]
Message-ID: <d92af18a-cd52-d7b3-0a1d-5ff6b72fb51d@proxmox.com> (raw)
In-Reply-To: <20220420141930.1626073-2-aderumier@odiso.com>

On 20.04.22 16:19, Alexandre Derumier wrote:
> Currently, when multiple exit-nodes are defined, each exit-nodes exchanges
> their own default route, so traffic is looping between both exit nodes
> instead going out.
> 
> This add a new route-map to filter received type-5 on exit node
> 
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
>  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(-)
> 
>

applied, thanks!

I'd do a bump of pve-network now for the upcomming point release, do you have anything
left that should go in (or was forgotten to be reviewed+applied)?




      reply	other threads:[~2022-04-27  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 14:19 [pve-devel] [PATCH pve-network 0/1] " Alexandre Derumier
2022-04-20 14:19 ` [pve-devel] [PATCH pve-network 1/1] " Alexandre Derumier
2022-04-27  8:34   ` Thomas Lamprecht [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=d92af18a-cd52-d7b3-0a1d-5ff6b72fb51d@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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 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