Now that we have a staging version of the website, this is no longer an issue.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 29 2021
Still reproducible in 1.3.0-rc5.
Source translations are showed correctly as of 1.3.0-rc5. Destination NAT needs verification.
It was a lot of problems with high CPU utilization with these mibs T1705.
https://forum.vyos.io/t/high-cpu-usage-by-bgpd-when-snmp-is-active
Jul 28 2021
Jul 27 2021
Wireguard has its own fwmark setting, such as:
@fetzerms The feature "policy local-route" in the 1.3/1.4 only.
Jul 26 2021
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:
I think we need to reopen this task. Sometimes (one per hour) some users and I got similar messages on version 1.3-rc4/rc5
Jul 25 2021
Put in a PR for this....
Jul 24 2021
Does disabling of vyos-configd has any impact in production?
Jul 23 2021
Have tried as you suggested, and confirmed it works.
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.
The latest .deb with fixed in pr above
It happens on different versions and not fixed in the latest version.
Jul 22 2021
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.
I think it is already fixed in T3674
@ramaxlo You can try to set this workaround:
In T3694#98436, @ernstjo wrote:How to get the debug logs? I already enabled debug mode.