Jessie based VyOS - Crux
Wed, Mar 22
Tue, Mar 7
Sep 18 2022
Sep 13 2022
This is also an issue on the 1.3.x builds due to a similar issue. See https://github.com/jordansissel/fpm/issues/1923
Sep 8 2022
Aug 29 2022
Aug 15 2022
Aug 2 2022
Hi friends, I'm experiencing what appears to be the same bug. In my case, it's on a redirect on a vif subinterface on a bonding interface. So perhaps bug is not so much about PPPoE interfaces, so much as any interfaces that don't exist before the commit is done.
Jun 28 2022
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
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
[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.