No issue on 1.4-rolling-202107191536 and later.

This is already available in VyOS 1.4

Can you please try running this test on a more recent VyOS version?

brctl is a deprecated package and superseeded by iproute2. Commands will be adjusted, thanks for reporting.

You can find the test here: https://github.com/vyos/vyos-1x/blob/current/smoketest/scripts/cli/test_interfaces_openvpn.py

Unfortunately I had to revert this PR as it broke the smoketests and also triggered the following OpenVPN error:

Most likely related to T3505

thanks for your detailed bisection of this issue. You mind submitting a GitHub PullRequest as per https://docs.vyos.io/en/equuleus/contributing/development.html?

I did a short lab test using the following topology based on my assumptions what you wan't to do:

@Viacheslav but that sounds more of a decent FRR bug. We could still consider adding EIGRP support for 1.4

Backported fix from T3637

I can confirm this on the latest rolling versions, seems to be a problem with the IPSec rewrite/move to swanctl.conf.

Thanks for the confirmTion

@dongjunbo this is a very very basic PR for VyOS 1.4 with the goal to implement this into the main VyOS release.

https://github.com/vyos/vyos-1x/pull/908

https://github.com/vyos/vyos-1x/pull/908

Commands are implemented.

Added command set service conntrack-sync interface <intrerface> port <port>

conntrtack implementation changed form 1.3 -> 1.4 by a rewrite. Can you please tell us which version of VyOS you are using?

Should be addresses using the new vyos smoketest shim from 1.4 branch.

Please share your configuration.

Please share your entire setup then somwe are able to help out.

please stop the idea of "deprecated" command. VyOS commands are in no relation to FRR commands.
If (and when) the FRR syntax changes, we will ensure it will still work by either migrating the VyOS CLI configuration dynamically on upgrade or by adjusting to the FRR configuration "under the hood" with our Jinja2 template.

the new build is already available. I am unsure if this works or is even supported by FRR.

Bug confirmed and fixed,

even if FRR manual states the deprecation notice, we have our own layer of abstraction and will deal with it once it is required.
For the time beeing, I just checked the commands (using tab completion).

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

What would be the "full set" up supported characters? If I remember correctly this regex is inherited from VyOS 1.1

Please share your Cisco and VyOS config, and also the Cisco router Model/Version

THis is infact only relevant when IPv6 addressing is used.

I ver much like this idea. Certificates can then easily be migrated from device to device, and very easy be referenced in a service.