Relevant PR:

@zsdc Yeah I see the bug now, I made the assumption that the config level by default was set to the bond (i.e. interfaces bonding bondX), good catch. Tested in a VM and I can confirm no regression in existing bonding behavior.

I agree that internal logic can be better, but I think that in this specific case the problem is much simpler: https://github.com/vyos/vyos-1x/pull/1708

I couldn't find an effective way to get all the new members added to the bond via config at commit-time without comparing the members to the running/effective config (the function leaf_node_changed() only gets the removed interfaces). Not doing so either causes runtime commit failures (where the bond fails to add/remove members) or boot failures (where the bond fails to add all it's members on boot).

Did you tried no bgp network import-check ?

FRR issues regarding this incorrect behavior ,

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

Related task IPsec syntax overhaul T4118

As I understand it is impossible directly with config option but possible with module omudpspoof

It works. The user connections persist over a reload and configuration changes causes a reload instead of a restart!
Thank you.

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

Started a PR for this: https://github.com/vyos/vyos-1x/pull/1702

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

@klase It is already in the latest rolling release. Could you re-check?

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

https://github.com/vyos/vyos-vm-images/pull/35

This works,
but if this is the new syntax the cli needs some cleanup.

According to this https://forum.vyos.io/t/vagrant-auth-failure-on-new-vagrant-images/9871/2
This issue is due to T874.
My understanding is that is not changeable, so my proposal is to add the "vagrant insecure key" for the vyos user during the vagrant box creation.

use the next syntax

show bgp ipv4 neighbors x.x.x.x advertised-routes

PR for show/reset functions:
https://github.com/vyos/vyos-1x/pull/1699

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

vyos@r14# cat /run/accel-pppd/l2tp.conf | grep dae-s
dae-server=127.0.0.1:1700,testing123
[edit]
vyos@r14#

I can confirm the firewall errors are fixed in the newest rolling VyOS 1.4-rolling-202212070318

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

Yes they are. 192.168.101.10 - is an ip of vpn remote access subscriber. He's connected to interface l2tp0 (accel-ppp). And i'm just trying to open tcp connection to port 80 on client from peer node.

@aserkin Thanks
Do l2tp clients in the network 192.168.101.x ? And you are trying to connect to some web resource behind l2tp?

The firewall settings does not seem to catch the traffic going out of l2tp* interfaces.

admin@vyos-lns-1:~$ show config commands |grep firewall
set firewall interface l2tp* out name 'nodefw'
set firewall log-martians 'disable'
set firewall name nodefw rule 100 action 'accept'
set firewall name nodefw rule 100 protocol 'tcp'
set firewall name nodefw rule 100 tcp flags syn
set firewall name nodefw rule 100 tcp mss '1300'

Oops. Thank you Nicolas.
Suddenly found myself far behind the current rolling release. Will upgrade first.

I have made the change in my configuration and tested as many configuration changes as I could (I have not tested radius authentication, and other options that are not valid in my setup) and it seems to work with this change without any unwanted side effects.

@dmbaturin It shows only IPv4 routes
Could you also add IPv6?