We'll update the key and make a post about it soon, sorry for the lengthy mix-up.

comments above are for https://vyos.net/get/nightly-builds/

@jestabro I have tested my usecase now and it seems the problem is fixed and the API no longer segfaults. Thank you so much for the fix and the fantastic turn around on this.

PR for 1.5: https://github.com/vyos/vyos-1x/pull/3137

@m.serdienis Add set of configuration commands to reproduce.

I don't think it is expected to get speed to the node itself.
A router is generally used for forwarding traffic. It is better to use iperf to check the speed between 2 hosts.

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

set service config-sync mode 'load'
set service config-sync secondary address '192.0.2.1'
set service config-sync secondary key 'xxx'
set service config-sync section firewall
set service config-sync section interfaces pseudo-ethernet
set service config-sync section interfaces virtual-ethernet
set service config-sync section nat
set service config-sync section nat66
set service config-sync section protocols static
set service config-sync section pki
set service config-sync section vrf

Change some section:

vyos@r4# set nat source rule 100 outbound-interface name 'eth0'
[edit]
vyos@r4# set nat source rule 100 source address '10.0.0.0/24'
[edit]
vyos@r4# set nat source rule 100 translation address 'masquerade'
[edit]
vyos@r4# commit
INFO:vyos_config_sync:Config synchronization: Mode=load, Secondary=192.0.2.1
[edit]
vyos@r4#

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

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

I have tested FRR NHRP with IPv6 as an overlay and I found some issues.

Can we let local-route support group options both in destination and source ?

set policy local-route rule 10 destination
Possible completions:
+  address              IPv4 address or prefix
   port                 Port number used by connection

PR for 1.4 https://github.com/vyos/vyos-build/pull/528

Close the task due to the reporter not responding.
Reopen if you still have this bug.

Seems fixed, checked on VyOS 1.5-rolling-202403110024

vyos@r4# rollback 
Possible completions:
  <N>	Rollback to revision N (currently requires reboot)

The similar task T5956

For 1.3 you have to add a separate PR

Do we need it for 1.3?
If yes, a separate PR should exist, as a backport is impossible.

Just wanted to follow up: I have now tested this and can confirm that everything is working as expected.