@skoenman Could you write some examples of configuration?

@Usman there is a root task for op-mode rewriting https://phabricator.vyos.net/T4564
https://github.com/vyos/vyos-1x/blob/1042fc32c371a74f048ffaf9a551b5d13c227f45/src/op_mode/bgp.py#L77-L80

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

@Usman You have to update to the latest rolling.
https://vyos.net/get/nightly-builds/

Hi perhaps it is better to get JSON format

PR 1.4 https://github.com/vyos/vyos-1x/pull/1804
PR 1.3 https://github.com/vyos/vyos-1x/pull/1806

Why did you delete this option and add a static route? Is there any use case?

This option has more priority than others.

Rewritten in 1.4
We are not planning to modify it in 1.3

Got it; it is impossible for now after this migration https://phabricator.vyos.net/T3090
We are working on the re-design firewall CLI

Setting it configurable will be a good solution.
Just like it is done in OpenVPN

vyos@r14# set interfaces openvpn vtun0 tls tls-version-min 
Possible completions:
   1.0                  TLS v1.0
   1.1                  TLS v1.1
   1.2                  TLS v1.2
   1.3                  TLS v1.3

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

@c-po @ordex Do you know how to integrate sources with our build system?

@daniil Could you update the PR?

Could you send the full accel-ppp working configuration that you expect?

@Jimz Show please the file cat /config/dhcpd.leases
I cannot reproduce it even if no any leases

vyos@r14:~$ show dhcp server leases 
IP Address    MAC address    State    Lease start    Lease expiration    Remaining    Pool    Hostname
------------  -------------  -------  -------------  ------------------  -----------  ------  ----------
vyos@r14:~$

There are some limitations

In particular, this is a list (may not be complete) of features that are not available when using ovpn-dco:

accel-ppp doesn't support FQDN for RADIUS https://docs.accel-ppp.org/en/latest/configuration/radius.html#radius
So it is impossible until it is available in the accep-ppp

Will be fixed in the next rolling release

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

Ok I'll re-check with the latest rolling.

r14# show version 
FRRouting 8.4.2 (r14) on Linux(6.1.6-amd64-vyos).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

The Original FRR log
This command is only supported under EVPN VRF

r14# conf t
r14(config)# router bgp 65000
r14(config-router)# address-family l2vpn evpn 
r14(config-router-af)# 
r14(config-router-af)# vni 100
r14(config-router-af-vni)# 
r14(config-router-af-vni)# route-target import 65000:100
This command is only supported under EVPN VRF
r14(config-router-af-vni)#

PR https://github.com/vyos/vyos-build/pull/298

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

updated actual PR https://github.com/vyos/vyos-1x/pull/1761

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

We should backport it to 1.3

PR https://github.com/vyos/vyos-1x/pull/1757
PR https://github.com/vyos/vyatta-cfg-system/pull/195

See tasks T1700 T2943

So there are 2 options

1. Live it as it is, it works as before (but maybe it is a legacy way)
2. Return the strongswan.service and use it in all required places (conf-mode, op-mode, dmvpn scripts, etc). So old ipsec/starter must not be overlapped with strongswan.service restarts