@dotAndy Is it still relevant?
Can you create a PR?

@SquirePug re-check please with the latest rolling image.

@jmaslak can you check the latest rolling image?

@kroy can you re-test this case?

Closed invalid - this is done with nftables now.

Related topic https://github.com/Chion82/netfilter-full-cone-nat/issues/42

It would be handy if the GARP announcement wouldnt be a separate list but rather picked up from any DNAT or SNAT rules.

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

Probably related:

In T6247#184232, @jmoore wrote:

. We need the feature regardless of the state of the repository.

It very may well have been. That's not really relevant to this request. The repository is an example. We need the feature regardless of the state of the repository.

I saw such repository more than once, but it seems that it has been abandoned. Last commit is dated two years ago.

Another example on nftables: https://github.com/fullcone-nat-nftables/nftables-1.0.5-with-fullcone

We do not use iptables and their modules for new features.
Feel free to add PR for nftables or if you know which commands should be for nftables

From initial PR these two feedback points are now implemented. PR has been amended see https://github.com/vyos/vyos-1x/pull/3307

I think I might've found the cause of this issue: the vni is unset from all VRFs when making changes. I posted a message about this on Slack (and about another, fairly similar, issue) on Slack about this.

Just checked with the current rolling release 1.5-rolling-202404141045. After committing set high-availability disable, keepalived is successfully stopped and the logs show that the transition script seems to be executed:

thank you very much for your analysis. I am still wondering, why it breaks with adding the vrf and why it works before.
Also, why it starts to work again, after rebooting when removing the vrf again (but not before rebooting)

Needs the original file with OpenVPN addresses/statistics which are parsed /run/openvpn/{interface}.status
Without it, it will be difficult to do something.

It is not related to VRF at all and is related to the policy routing logic:
Reproduced even on 1.3.2

set interfaces ethernet eth1 address '192.168.122.14/24'

Updates have been applied on 1.4 and 1.5.

This can probably be closed.

I decided to dig into this a little more and try to trace this out:

sudo nft add chain inet vrf_zones trace_chain { type filter hook prerouting priority -301\; }
sudo nft add rule inet vrf_zones trace_chain meta nftrace set 1

@dmbaturin, @sever
Would love your input regarding the lack of headers when using the -c option. I've created a PoC around "chronyc -c activity" as it was the most straight forward command to start with.

@dmbaturin , @Viacheslav - I use debian snapshot repository when building VyOS LTS on my own.

side note, if you flush ruleset, and only add:

Something I just figured out is that the minute I do:

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

The regression causing 'image cannot be found" was fixed in https://vyos.dev/T6186.

PR:
https://github.com/vyos/vyos-http-api-tools/pull/11