please, read the guidelines that I shared, the point here if it works with our system , is not error in cli structure o functionality you should open a forum topic or support case (in case you have an active subscription), before opening a task here that is not clear.(without configuration ,debug attached or packet capture)

please , read the guidelines on this post . it doesn't see a bug if not a support task:

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

@mersl thanks for confirm.

we've added this ability to configure the topology on isis :

agree ,it's more a feature than a bug : PR https://github.com/vyos/vyos-1x/pull/3537

the problem here is that MT options is enable by default when the RIB has ipv4, if not not-MT is enable by default on IPv4 .So, you need to add additional topologies (ipv6-unicast , ipv6-multicast,etc)

tested new cli structure, it combine the new mach-group and old syntax :

I've tested and now is working correctly :

add documentation : https://github.com/vyos/vyos-documentation/pull/1444

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

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

this new command was merge in order to solved this problem :

vyos@vrf-test:~$ show configuration commands | match disable
set protocols bgp parameters disable-ebgp-connected-route-check

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

it think that we can use also something similar to what we use ocserv to generate ssl certificates:

it makes seens , agree with add a Config Error to do not allow both options simultaneously ,.

as I mentioned , it was added in 9.1 as default behavior :

this command was added by default in FRR , but it's supported on lasted version (9.1):

i've re-checked with the new image from GCP and new cloud-init version , it seems to be working as expexted :

this fix is not merge yet : https://github.com/vyos/vyatta-op-vpn/pull/37

some improvements were added in this task , enable or disable the http security headers in the openconnect configuration :

when it's merge , I will test with the controller to see if we are able to get BMP with the new FRR version.

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

tested on 1.5/1.4 :

PR 1.5/1.4 : https://github.com/vyos/vyos-1x/pull/2564

Do you tested it ? using our current rolling-release

I'll hava a lab with PIM SSM and BFD , I'll update our documentation with those feature with example.

I've tested this flag in both version 1.4 / 1.5 , it seems to work as expected :

tested on 1.4-rolling-202311080309

it's not a bug, this command are able in ospf :

@devon

after merge this ldp bug fixed , I saw that now it's already working . Could you check it ? I've tested on a lab and it seems to work :

tested /resolved

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

@jvoss thanks to confirm !

I've tested this issues in our lasted rolling-realese , after last commit , it seems works without problems :

vyos@vyos# load test.conf
Loading configuration from 'test.conf'
Load complete. Use 'commit' to make changes effective.
[edit]
vyos@vyos# compare
[policy]
+ route-map TEST {
+     rule 10 {
+         action "permit"
+         set {
+             community {
+                 add "65001:1"
+             }
+             large-community {
+                 add "4200000000:100:1"
+             }
+         }
+     }
+ }

exactly , i'll give an example of what is the improving (or new cli) , we have a policy where we can mach different DSCPs associate with REAL TIME or VIOCE . Current in our cli , it would be something like this :

this case was resolved lasted configuration done .

this task is a re-definition from a traffic class , I think it could be more clear if we separate tc-filter in a class-map , so we can define different profiles in our cli based on services :

I think we can do something similar to it : https://alestic.com/2018/12/aws-ssm-parameter-store-git-key/

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

for me , it's ok . I didn't see another issue related it . we can close

@sdev greats !!!

command on 1.5 :

@vfreex I've tested in my labs related this issues , I can confirm that it work as expected . this original zone solved the problem when there was a src-nat /dst-nat with different VRFs or leaking with them ,Thanks you for this contribution .

@sdev take a look over these repository :