I've made some tested, it seems works as we expected :

as we talked , this behavior is the same on vyos1.3.x/frr7.5.x . the main difference is that on vyos-cli doesn't add this command .

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

normally, when I want to make an empty-base config, I save config.boot another place. So I load it when I need to restart the configuration. I was thinking that we can make something like it by cli, it should be saved in the first config.boot file and restored.

as I remember ... it has been working by this PR:

I've re-tested this issues with the initial configuration, nat source / mesquered/ destination , it seems to work as @Dmitry said. The conntrack doesn't show the connection as [UNREPLIED] , it's established :

@Viacheslav thanks

it's a common behavior when you want to set sysctl variable and bash-cli is used ( vyos-cli by default when restart the vm set this value in 0 ) . however , it's possible to configure it with this command :

i've checked this issues, it seems to be solved . I think that it was solved for another task. I used the following vyos version :

yes, it was added on this version vyos-1.4-rolling-202205311706, please check again

We've added this feature in our latest nightly building release, could you check it ?

PR for 1.4 Sagitta branch https://github.com/vyos/vyos-1x/pull/1337

I've tried with a new spoke and I can't seem to register using `reload-or-restart', although it resolved the lost connectivity issues the opennhrp process needs a full restart. however, if you restart opennhrp daemon it causes different issues and usually the spoke loses connection.

## hub

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

I did this change as you mentioned and it worked, , example:

Hub basic setting :

Yes ,you need to reload the services and it works , here's an basic example with the current configuration :

sorry for my late reply , I've been testing this case and I could replicate the same behavior

regarding this behavior , I found a similar task where there was a bug with chain VYOS_PRE_SNAT_HOOK that jumps to WANLOADBALANCE ,although it was solved .
However , policy traffic rule seems to be affected with this issues(the main difference is that now there is a pass on this chain/ POSTROUTING) , below I'll share the task just to know where you can find the problem.

I've been testing , the feature works as expected . IPOE assigns different ip by dhcp using ip-pool :

vyos@ipoe:~$ show ipoe-server sessions
ifname     | username |    calling-sid    |     ip     | rate-limit | type | comp | state  |  uptime
---------------+----------+-------------------+------------+------------+------+------+--------+----------
 eth3.1000.140 |          | aa:bb:cc:00:60:00 | 10.10.10.0 |            | ipoe |      | active | 00:03:44
 eth3.1000.130 |          | aa:bb:cc:00:50:00 | 10.10.10.2 |            | ipoe |      | active | 00:

there is another possible to achieve the desired result , it's using this radius-option:

I've been testing , now we are able to configure BMP with load configuration .in latest version 8.2.2(they solved these issues)

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

this issue with frr.reload.py keeps happening with stable/8.1 , we'll try it when 8.2 is stable.

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

I think it is necessary to show this kind information . it should use tools/service as netflow/ipfix . for example:

we found an error when we tried to upload the configuration using the frr.reload.py . I did an issues request to FRR with this problem ,here is the case:

I think there is a bit of confusion here. nowadays 1.4 it's works as you mention , but 1.3 doesn't remove static (so we can see both static in the RIB) . however, In my personal opinion , it should show both static in our cli (same also on FRR) , because it's possible that you may need a different prefix ,it'll be installed with a different next-hop .

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

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

yes, you are right:

yes , i'm using this version :

I've checked with this new build , it works with validator ranges/port :

I've been testing and it works :

well , I think it should be something like this :

this PR https://github.com/vyos/vyos-1x/pull/1088 only include how to enable daemon , but it doesn't add VyOS-cli commands in BGP (the daemon only allows you to enable it).

I want to leave a comment , it's also common that customers don't know that PVST is enabled by default (and send bpdu peer VLANS), So it's possible to mitigate it also using nf rules , below leave a example:

thanks you @Viacheslav

Yes, It seems that rfc doesn't work , also I found this issues :
https://github.com/FRRouting/frr/issues/5824

In the real-world to avoid it they used cluster-id / a session BGP between them , it's the idea of RR :

not yet , we 've been trying with different CT but it's not solve the main problem . I understand that disabling conntrack is not possible because is used for nat.

and It's the way to set on Vyos:

set protocols bgp <asn> parameters cluster-id <id>

there is a recommendation that if you use RR in the same hierarchy and avoid loop , we need to set 'cluster-id'

yes, It is an issues related with the conntrack+ nat/vrf leak , I share something where the problem is clearer :

I have a good news, we already able to setting vpnv4 on Vyos ! thanks for your support , I was testing it and didn't have problems .let me show:

@c-po Thanks!!! :)