I would prefer a different syntax, in order to avoid the necessity attaching it to an interface. Maybe something like:

Error detected in forum: https://forum.vyos.io/t/unable-to-query-snmp-anymore-in-a-more-recent-1-4-version/10388/3
Fix for that bug: https://github.com/vyos/vyos-1x/pull/1805

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.

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

I built a 1.4 ISO after my change was merged and deployed it to my home network. Setting a restrictive allow list works as expected, only the allowed IPs/subnets are able to use NTP. Removing all allow IPs prevents chrony/ntp from even listening to port 123. I don't think the "deny all" is needed in the code at all, but it is also not preventing the service to run as expected so I'll leave it.

@c-po is this an S3 bucket policy issue, or do the files not exist?

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

We also need to increase opened file descriptors (ulimit -n) to listen limit + some margin.
And consider adding a warning about increasing net.core.optmem_max for systems with a limit of more than 100 peers.

It is a problem with mapping user to radius_priv_user
This problem began after https://github.com/vyos/vyos-1x/commit/765f84386b6e94984ff79db2eab36d51f759159b#diff-0ab0ed71ce757261c4a6ae2f3a5bc441d6257d477bfb5435ae38f230777ff81cR51
If I set in sshd_config

I'm not free now. I'll check it when I'm free

@Viacheslav unfortunately I am not too familiar with your build system, but basically you need to clone the ovpn-dco repository (https://github.com/OpenVPN/ovpn-dco.git) and compile it against your kernel, as you would normally do for any other out-of-tree kernel module.

PR for alternative completion helper. This provides the same args/output of the Python script, with a speedup of 1--2 orders of magnitude; testing needed.
https://github.com/vyos/vyos-utils/pull/11

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

A basic implementation: https://github.com/vyos/vyos-1x/pull/1800

when an incompatible option is found, OpenVPN will simply disable DCO and go back to tun (this info will be logged). Therefore the limitations should not be a reason for not including DCO in VyOS.

PR for 1.3 which makes the change available for every config subsystem https://github.com/vyos/vyos-1x/pull/1798

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

In T3871#141847, @jestabro wrote:

Before adopting the approach mentioned above, there was development of an alternative using pyudev within an 'interface-monitor' daemon; the following branches contain (a version of) the rebased code. It would need a few hours of attention to check the logic and add the is_persistent check from vyos-interface-rescan.py; it could use some refactoring as well.

https://github.com/vyos/vyos-1x/compare/current...jestabro:vyos-1x:interface-monitor
https://github.com/vyos/vyatta-cfg/compare/current...jestabro:vyatta-cfg:interface-monitor
https://github.com/vyos/vyos-build/compare/current...jestabro:vyos-build:interface-monitor

Before adopting the approach mentioned above, there was development of an alternative using pyudev within an 'interface-monitor' daemon; the following branches contain (a version of) the rebased code. It would need a few hours of attention to check the logic and add the is_persistent check from vyos-interface-rescan.py; it could use some refactoring as well.

@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:~$

The approach in commit ee02ca93 of vyos-1x was considered a reasonable workaround for all but a few corner cases. However, the issue pointed out in

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

PR for 1.4: https://github.com/vyos/vyos-1x/pull/1795

pfsense implements it , however , they explain that it has some limitations :

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

PR for Equuleus:
https://github.com/vyos/vyos-build/pull/303

PR for Sagitta:
https://github.com/vyos/vyos-build/pull/301

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

Going to close this task as the PR has been merged into vyos-1x, and documentation has been merged also - https://docs.vyos.io/en/latest/configuration/vpn/openconnect.html#configuring-radius-accounting

Will be fixed in the next rolling release

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

Is it possible to also add some logic to populate boot entries using https://uapi-group.org/specifications/specs/boot_loader_specification/ ? I have been experimenting with systemd-boot, and it's working fine apart from the missing loader files. Those files look something like this:
/usr/lib/live/mount/persistence/loader/entries/1.4-rolling-202210050218-vty.conf

title     "VyOS 1.4-rolling-202210050218 (KVM console)"
version   1.4-rolling-202210050218
options   boot=live quiet rootdelay=5 noautologin net.ifnames=0 biosdevname=0 vyos-union=/boot/1.4-rolling-202210050218 console=tty0
linux     boot/1.4-rolling-202210050218/vmlinuz
initrd    boot/1.4-rolling-202210050218/initrd.img

There will be similar files for serial and USB console.

Fixed in commit: https://github.com/vyos/vyos-1x/commit/6eea12512e59cc28f5c2e5ca5ec7e9e7b21731da