KeyboardInterrupt is caught with an appropriate error message now.

What is the difference between local router and failover router? It is not clear. My local router in failover mode ;) but state master.

Backport to 1.4?

And going further, we may create an extra column, in order to print if the lease was granted by Local-Router or by fail-over router..
Example:

Changing this line: https://github.com/vyos/vyos-1x/blob/current/src/op_mode/dhcp.py#L117C9-L117C107

Do you want to see leases state == backup?
What is the expected?

Pretty sure some preceding backports are pending. Please give me a couple of days. I plan to sync up 1.4 with 1.5 and update the docs.

Looks like this has been resolved using the latest 1.4 nftables. I am now able to specify local time without the use of UTC.

We'll discuss this internally, but for sure a fix should be applied.
Thanks for such a detailed bug-report.

PR https://github.com/vyos/vyos-build/pull/459

Agree with @Viacheslav and @GurliGebis comments above.

I agree, without it, you end up repeating yourself alot, with the established, related and invalid rules.
As long as they are applied before the zone specific rules (which is how I guess it used to work), it makes sense.

There are different commands

vyos@r1:~$ show bgp neighbors 192.168.122.14 advertised-routes 
% No such neighbor or address family
vyos@r1:~$ 
vyos@r1:~$ show ip  bgp neighbors 192.168.122.14 advertised-routes 
vyos@r1:~$

Should we return global state policy?
It was useful.

Tested in VyOS 1.4-rolling-202311100309:

Tested in VyOS 1.4-rolling-202311100309
Configs:
Node-1

Backport to 1.4 has conflicts https://github.com/vyos/vyos-1x/pull/2533

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

@Viacheslav
I missed running git pull on my ansible execution node. Works as it should. Thank you!