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.

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).

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

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.

@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?

Any chance this will be revived for 1.3 or 2.0 ?
Any amount of firewalling is not gonna stop brute forcing.

No problem occured after updating another machine from version VyOS 1.2-rolling-201910102056 to 1.3-rolling-202006230700. Login succeeded after reboot immediately.

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.

Change your OSPF network type to broadcast. I had the exact same issue with a Cisco 877 Client with a VYOS hub.

Confirmed working again (using rolling from 2019-01-29). Thank you for verification.

Can't reproduce

Works for me in the latest build.

vyos@vyos-test-2# set protocols static route6 ::/0 blackhole distance 10
[edit]
vyos@vyos-test-2# commit
[edit]
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)

Can´t reproduce

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

Hello guys.
Unfortunately the syntax error is when typing the command.

also tried the same on VyOS 1.2.0-rolling+201811240337, it's ok.