Dec 3 2024
Nov 16 2024
For support requests, use forum.vyos.io
Use forum.vyos.io for support requests
Oct 8 2024
Jul 3 2024
Since the task as worded is no actionable, I'm closing it as invalid. I'm not against using any tools that might help us, but we need to be sure what the task is (e.g., to implement regular scanning, or to fix specific suggestions from a scan...).
Apr 12 2024
Apr 4 2024
The situation is significantly more complicated now that we have libvyosconfig, but the smoketest infrastructure is also much better. The original wording no longer applies.
Feb 17 2024
The validator correctly handled addresses that end with zero if they valid host addresses. It rejects such addresses iff they are the first addresses of their subnets: in IPv4 because it's the network address, in IPv6 because it's the Subnet-Router anycast address (https://www.rfc-editor.org/rfc/rfc4291#section-2.6.1).
Mar 8 2023
For "SSH" we have dynamic-protection
vyos@r14# set service ssh dynamic-protection Possible completions: + allow-from Always allow inbound connections from these systems block-time Block source IP in seconds. Subsequent blocks increase by a factor of 1.5 (default: 120) detect-time Remember source IP in seconds before reset their score (default: 1800) threshold Block source IP when their cumulative attack score exceeds threshold (default: 30)
+1 for implementation
Oct 17 2021
Sep 10 2021
Sep 3 2021
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
Can't reproduce