PR: https://github.com/vyos/vyos-nhrp/pull/6

Properly works on the latest 1.4 rolling. Is it possible to backport changes to 1.3?

@Viacheslav Done. Looks to be working fine in VyOS 1.4-rolling-202105250417

@sever Done. Looks to be working fine in VyOS 1.4-rolling-202105250417

We are seeing this on an X722 NIC that's still the i40e driver (the server in question also has an X710 NIC, but there's no cables connected to the X710 but I should be able to get cables connected to the X710 next week). We are using 1.4 on this machine.

That mist actually be habdled by vbash and the backend code.

I propose something like

set service pppoe-server extended-scripts on-pre-up <path>
set service pppoe-server extended-scripts on-up <path>
set service pppoe-server extended-scripts on-down <path>
set service pppoe-server extended-scripts on-change <path>

FRR doing normalization for ipv6

Unfortunately, I can't reproduce it.
Also, all smoke test for static routes looks good.

@olofl Add please a separate task for JSON.

As I understand the needed section

[pppd-compat]
verbose=1
#ip-pre-up=/etc/ppp/ip-pre-up
ip-up=/etc/ppp/ip-up
ip-down=/etc/ppp/ip-down
#ip-change=/etc/ppp/ip-change
radattr-prefix=/var/run/radattr
#fork-limit=16

@masimo Can you check/test it?

@Viacheslav We have been running the new rolling realse in the lab since 24th May with no issues. Thanks for help.

VyOS 1.4:
https://github.com/vyos/vyatta-cfg-firewall/pull/23

Providing an entire path of the file i.e. /opt/vyatta/etc/key-pair.template instead of "@sysconfdir@/key-pair.template", makes the command executable.
IPSec VPN in X509 mode needs ca cert file, also server/client cert has to be signed by the CA for identification.
So, maybe rewriting this script will be helpful.
Any suggestions are welcome.