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.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 24 2023
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.
Nov 23 2023
We'll discuss this internally, but for sure a fix should be applied.
Thanks for such a detailed bug-report.
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
Nov 22 2023
@Viacheslav
I missed running git pull on my ansible execution node. Works as it should. Thank you!
A fix that changes the behavior back to it was https://github.com/vyos/vyos-1x/pull/2527
PR for bridge: https://github.com/vyos/vyos-1x/pull/2528