This isn't reproducible in either up-to-date LTS or 1.3, so I assume the issue was fixed.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 29 2021
PR for 1.3 https://github.com/vyos/vyatta-cfg/pull/40
PR https://github.com/vyos/vyos-1x/pull/945
Also, need to cherry-pick it to Equuleus
Now that we have a staging version of the website, this is no longer an issue.
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?