PR: https://github.com/vyos/vyos-1x/pull/1168/

yes, you are right:

yes , i'm using this version :

I've checked with this new build , it works with validator ranges/port :

I've been testing and it works :

well , I think it should be something like this :

this PR https://github.com/vyos/vyos-1x/pull/1088 only include how to enable daemon , but it doesn't add VyOS-cli commands in BGP (the daemon only allows you to enable it).

I want to leave a comment , it's also common that customers don't know that PVST is enabled by default (and send bpdu peer VLANS), So it's possible to mitigate it also using nf rules , below leave a example:

thanks you @Viacheslav

Yes, It seems that rfc doesn't work , also I found this issues :
https://github.com/FRRouting/frr/issues/5824

In the real-world to avoid it they used cluster-id / a session BGP between them , it's the idea of RR :

not yet , we 've been trying with different CT but it's not solve the main problem . I understand that disabling conntrack is not possible because is used for nat.

and It's the way to set on Vyos:

set protocols bgp <asn> parameters cluster-id <id>

there is a recommendation that if you use RR in the same hierarchy and avoid loop , we need to set 'cluster-id'

yes, It is an issues related with the conntrack+ nat/vrf leak , I share something where the problem is clearer :

I have a good news, we already able to setting vpnv4 on Vyos ! thanks for your support , I was testing it and didn't have problems .let me show:

@c-po Thanks!!! :)

Thanks for you comment ! it's good consider that options

i've been testing this new feature in our last release and it works well :

Sure ! i'll test this feature and let you know !

thanks for your comment , we are testing first with @rherold , I understand that your case is similar but it's not the same (you have an explicit route-leaking between default vrf and vrf X ). So we also need to test it and try to sure the version solved it .

good lab, thanks for your time! I want to leave a comment , I used the syntax that you recommend and it worked well ( VyOS 1.3.0-rc5):

yes , but when you use 'set protocols static route 10.0.0.0/8 next-hop 1.1.1.1 next-hop-vrf red' it doesn't install the prefix in the default table :

Hi ruben

Hi ruben,

In T3657#97243, @c-po wrote:

I wonder why you use ebgp multihop wirh link local addresses?

I used it only for testing (but this command increment ttl in two).

I add an extra commentary , it is config on FRR:

yes, I am using the following version :

I 've been checking this behavior with a different password , also I used the same password as you . But I couldn't reproduce the issue , both cases i add $ in the word and change the hash, let me show :

I create PR to add this new feature with the syntax to vyos-cli and frr commnads ,

I think it is also related https://phabricator.vyos.net/T3522

I have checked that functionality , i can replicate the issues .although there is a workaround if you "set protocols static table 11 route 0.0.0.0/0 dhcp-interface " any interfaces , it doesn't see in your table ( table 10 /11 ) we can see theses routes in the default table , let me show :

Sorry for confusing with the status of the ticket , I wanted to put in pending . I was trying to replicate the issues in a lab environment but it wasn't possible , let me show :

In T3578#95246, @fernando wrote:

Hi

I tried to replicate that issue with the same version but I couldn't , let me show

vyos@vipv6-lp# run show version

Version: VyOS 1.4-rolling-202104270417
Release Train: sagitta

Built by: autobuild@vyos.net
Built on: Wed 28 Apr 2021 01:17 UTC

I`m Sorry! it maybe was an error that version , actually I try with Vyos 1.3-rc4 and It works well :

I can reproduce that behavior, although I use another VyOS version " VyOS 1.3-rolling-202104210642" with a virtual machine :

I can confirm that beheivor , settings on FRR :

Before that configuration , we should add the mpls settings in our cli-vyos , it is an example: