Fri, Sep 10
Fri, Sep 3
May 29 2021
Could you please make this a forum post instead? A bug report should come with precise description of wrong behaviour and reproducing steps: feel free to make one when that info is available.
Jul 18 2020
@c-po Why stop the implementation of this function? My original idea was to implement the automatic configuration and operation of the service in vyos-1x. It seems that you already have an idea?
Jul 6 2020
Any chance this will be revived for 1.3 or 2.0 ?
Any amount of firewalling is not gonna stop brute forcing.
Jun 24 2020
No problem occured after updating another machine from version VyOS 1.2-rolling-201910102056 to 1.3-rolling-202006230700. Login succeeded after reboot immediately.
Jun 23 2020
Just reproduced same issue on second system. Source VMware vSphere Host.
Same Problem here: After upgrading from 1.3-rolling-202005030117 to 1.3-rolling-202006230700 no login possible. After resetting password for admin user through password recovery login works. Rest of configuration was copied as should.
Apr 1 2020
Jan 26 2020
Jan 2 2020
Jan 1 2020
Sep 10 2019
Aug 31 2019
Jul 20 2019
Jul 11 2019
Jun 15 2019
May 18 2019
Mar 16 2019
Feb 4 2019
Change your OSPF network type to broadcast. I had the exact same issue with a Cisco 877 Client with a VYOS hub.
Jan 29 2019
Confirmed working again (using rolling from 2019-01-29). Thank you for verification.
Jan 27 2019
Works for me in the latest build.
vyos@vyos-test-2# set protocols static route6 ::/0 blackhole distance 10  vyos@vyos-test-2# commit  vyos@vyos-test-2# run show ipv6 route ::/0 Routing entry for ::/0 Known via "static", distance 10, metric 0, best Last update 00:00:10 ago * unreachable (blackhole)
Jan 25 2019
I think the phrasing is slightly misleading but ok!
It's still possible to build all from sources for free (of course you need to have skills for that)
and it's always will be open source.
So nothing to change basically
Nov 25 2018
Unfortunately the syntax error is when typing the command.
Nov 24 2018
also tried the same on VyOS 1.2.0-rolling+201811240337, it's ok.
Nov 9 2018
Nov 8 2018
Oct 29 2018
Great. At least now it is register (for 1.1.8) that this is fix under 1.2.0-rc4+. Thx