From: Gabriel Goller <g.goller@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v2 0/7] sdn: add BGP fabric
Date: Thu, 16 Apr 2026 18:49:40 +0200 [thread overview]
Message-ID: <4kztj6u4xmlswyg5odl4ktkbnlxre2jty3bzfry3t2sywuasuw@dwsgipr5faon> (raw)
In-Reply-To: <20260415111134.124720-1-h.laimer@proxmox.com>
Maybe this needs to be fixed in the EVPN series by Stefan, but...
When I have a evpn controller with a bgp fabric and multiple zones, the evpn
routes won't be distributed because we filter the bgp routes using `ip protocol
bgp ...` in the bgp fabric.
So we either need to add the VTEP IPs to the access-list (no idea if this works,
haven't tried it), or we need to remove the filtering altogether when a EVPN
controller on top of the fabric is added.
next prev parent reply other threads:[~2026-04-16 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:11 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
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
2026-04-16 16:49 ` Gabriel Goller [this message]
2026-04-16 16:57 ` [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v2 0/7] sdn: add BGP fabric 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=4kztj6u4xmlswyg5odl4ktkbnlxre2jty3bzfry3t2sywuasuw@dwsgipr5faon \
--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 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.