Jessie based VyOS - Crux
Details
Apr 7 2022
Trying to configure a wireguard peer with a dns name as remote endpoint. I understand this is not supported, but I see many references to creating a post-boot script to do this. Any working examples? Thank you
Apr 4 2022
I think all Chaos stater after this message:
Apr 1 2022
More detail :
I happened today in 17 vyos clusters after a switch failure. Same logs and no bgp process running:
Mar 28 2022
The below is also not possible on route maps
Mar 24 2022
Mar 7 2022
Resolved in https://phabricator.vyos.net/T3774, but it will not be backported to 1.2.
Feb 18 2022
@kirvio Could you check it on 1.3/1.4?
Feb 7 2022
Dec 29 2021
To reproduce:
set interfaces ethernet eth2 vif 35 set interfaces pppoe pppoe0 authentication password 'MYPASSWORD' set interfaces pppoe pppoe0 authentication user 'MYUSER' set interfaces pppoe pppoe0 default-route 'force' set interfaces pppoe pppoe0 mtu '1492' set interfaces pppoe pppoe0 redirect 'ifb0' set interfaces pppoe pppoe0 source-interface 'eth2.35' set interfaces pppoe pppoe0 traffic-policy out 'OUT2' set interfaces input ifb0
Commit:
[email protected]# commit [ interfaces pppoe pppoe0 redirect ifb0 ] Cannot find device "pppoe0" tc qdisc ingress failed at /opt/vyatta/sbin/vyatta-qos.pl line 334.
Dec 20 2021
@Viacheslav found the source of the restriction:
Dec 16 2021
Dec 5 2021
As both PRs have been merged now, I'm resolving this issue.
Dec 3 2021
Nov 19 2021
I would not call this a bug as this is produced on intention.
Nov 12 2021
Nov 6 2021
Nov 1 2021
Oct 29 2021
The issue even with 00:00 format
Oct 28 2021
The similar FRR tasks
https://github.com/FRRouting/frr/issues/9020
https://github.com/FRRouting/frr/issues/2350
Oct 23 2021
Reverted back to "4.19.195"
Oct 22 2021
https://github.com/vyos/vyos-build/commit/402d80498683f298be1dd3581cb0143362ceb561 - developers are reverting to kernel 4.19.207. But this is the kernel that started the problem.