Using timeouts is a pretty bad idea as they vary on the host CPU or utilisation of a hypervisor.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 31 2021
it should be timeout ~1.8 sec between adding ipv6 address and create l2tp interface
Jul 30 2021
As I see it's already fixed:
[email protected]# set protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 [edit] [email protected]# set protocols bgp 64512 neighbor 192.168.5.5 remote-as 64513 [edit] [email protected]# commit [ protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 ] local-as: 64513 and remote-as: 64513 can't be the same
PR for current https://github.com/vyos/vyos-1x/pull/949
Jul 29 2021
They should be disabled by default, but there must be the ability to re-enable OIDs back from CLI.
PR for 1.3 https://github.com/vyos/vyatta-cfg-quagga/pull/86
add option "solo" for neighbor.
PR https://github.com/vyos/vyos-1x/pull/945
Also, need to cherry-pick it to Equuleus
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:
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
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.