@fetzerms The feature "policy local-route" in the 1.3/1.4 only.

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

Thanks for the info. I think (indeed) that *might* work for wireguard. But never the less, it would be cool to have the possibility to route by fwmark.

We only have source routing now:

Put in a PR for this....

Does disabling of vyos-configd has any impact in production?

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

I can confirm that happens only if you ssh via vrf and set static route6 in default vrf
And it works without debug, if you stop vyos-configd service

I can reproduce this issue on different routers (Baremetal or VMs). Debug mode on, ipv6 routes install. Debug mode off, static route config is missing in frr, thus not installed into the kernel.

Do you use standard user (vyos) or not?
yes, standard vyos user

I can't reproduce it in any version.
Let's check what is different, and why only in your case do you have a problem, but other users never have this issue.

It happens on different versions and not fixed in the latest version.

No issue on 1.4-rolling-202107191536 and later.

Interesting. But I never saw it.
Can you check the latest rolling? I have no other ideas yet.

Just that shitty. When i enable debug mode route install works fine when i disable debugging i won't work.
I have that situation on multiple routers.

In T3694#98436, @ernstjo wrote:

How to get the debug logs? I already enabled debug mode.

Tested configuration:

set interfaces ethernet eth1 address '192.0.2.1/24'
set interfaces ethernet eth1 address 'dead:beef:b004:3::1/64'
set interfaces tunnel tun0 address '2a0f:5707:b004:3::1/64'
set interfaces tunnel tun0 encapsulation 'sit'
set interfaces tunnel tun0 parameters ip ttl '255'
set interfaces tunnel tun0 parameters ipv6 hoplimit '255'
set interfaces tunnel tun0 remote '192.0.2.2'
set interfaces tunnel tun0 source-address '192.0.2.1'
set protocols static route6 cafe:e1f:b046:1::/64 next-hop 2a0f:5707:b004:3::2
set protocols static route6 cafe:e1f:b046:c000::/56 next-hop 2a0f:5707:b004:3::2

How to get the debug logs? I already enabled debug mode.

Try to touch frr debug to collect more information
https://docs.vyos.io/en/latest/debugging.html#frr

It's a basic tunnel setup and also reproducible with routes which do not point to a tunnel interface and happens also with physical interfaces.

@ernstjo Can you share an example of your tunnel interface?
I don't understand yet how to reproduce it.
If you delete routes and add again, do you get the same result?

Unfortunately, it seems that the same problem still happened. Although it seems that the container can be started normally after restart due to priority adjustment and some factors, it is not a normal operation result!

PKI Wireguard PR: https://github.com/vyos/vyos-1x/pull/929

Can you send more examples how it looks like in podman cli?
Which parameters do you set, and how to check if it is successfully applied?

Can you please try running this test on a more recent VyOS version?

brctl is a deprecated package and superseeded by iproute2. Commands will be adjusted, thanks for reporting.