From: Cyrus <cyruspy@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Inter VRF traffic
Date: Tue, 11 Mar 2025 15:54:37 -0300 [thread overview]
Message-ID: <CAEaLa5Ge_VgGhjaVXKh7QDDaOuFcw+VTXsBjdGzKk9ERQSj+6Q@mail.gmail.com> (raw)
In-Reply-To: <CAEaLa5GNAxr=XHqU9V7+coAankHGqDB-hL_b9fBL34vH5qrNxg@mail.gmail.com>
On Tue, Mar 11, 2025, 14:44 Cyrus <cyruspy@gmail.com> wrote:
> On Tue, Mar 11, 2025, 13:41 DERUMIER, Alexandre <
> alexandre.derumier@groupe-cyllene.com> wrote:
>
>> Hi,
>>
>> >>I'm trying to make traffic work between VRFs passing through a an
>> >>external firewall (opnsense+frr) but traffic seems to be resolved
>> >>locally by the node, even though source/destination are on different
>> >>VRFs (and ultimately doesn't work):
>>
>> as you have defined exit-nodes, they are leaking routes between the
>> main vrf && the evpn zone vrf. (to be able to route traffic between the
>> evpn network and the real network)
>>
>>
>> if you want to announce evpn subnets to your opensense, you can create
>> an extra bgp controller for each node, and add your opensense ip as
>> peer. it should be enough.
>>
>
> Hello!,
>
> Now that you mention it.... Probably I don't need exit nodes to be defined.
>
> In this specific usecase, I'm placing peering interfaces in the specific
> VRFs and configuring 2 manual BGP instances towards the firewalls.
>
> That might fix my current problem. Will try and report back!
>
> Regards.
>
That was it!!!!, thanks for your comments.
I removed my exit nodes from the zone configuration and kept my manual BGP
peers (1 set per VRF) towards the external NE (not supporting EVPN).
Regards.
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-03-11 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 20:39 Cyrus
2025-03-11 7:50 ` Schunke, Alexander
2025-03-11 16:25 ` DERUMIER, Alexandre
2025-03-11 17:44 ` Cyrus
2025-03-11 18:54 ` Cyrus [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=CAEaLa5Ge_VgGhjaVXKh7QDDaOuFcw+VTXsBjdGzKk9ERQSj+6Q@mail.gmail.com \
--to=cyruspy@gmail.com \
--cc=pve-user@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