ferm VS RdpGuard

I remember hating shorewall and similar ones because, well, I know iptables, and I know exactly what I want so using anything that tries to abstract it into it's own approach is torture as I need to take the rules I want and translate it to whatever mediocre paradigm shorewall (or ufw, or near-any other firewall manager in the wild) decided to put on top of iptables. I ended up using ferm... - Source: Hacker News / 10 months ago

I'm a big fan of ferm. Many major distros have it readily available as a package, and it makes for beautifully readable firewall definitions. Source: about 1 year ago

The last time I needed to do complex iptables stuff, I found FERM really helpful. The structured config language greatly reduces the amount of boilerplate code you have to type, while still having a pretty direct mapping to the emitted iptables rules. A bit like compiling sass to css. Source: about 2 years ago

Also just about last thing I want is to deploy another configuration management system alongside the system that manages everything else on machine. Currently we just use Puppet to deploy ferm rules (which is best described as "iptables+", naming convention and such are still iptables-like but a lot of macros/syntax sugar around it). Source: almost 3 years ago

Another option is limiting login attempts with RDPGuard. Source: about 1 year ago

This sounds like a good use for RDPGuard: https://rdpguard.com/. Source: almost 2 years ago

Using a different approach RDPguard helps a lot. https://rdpguard.com/. Source: about 2 years ago

Oct 4 11:59:49 filter bash: WARN [10-04 11:59:49] - SeverProtection.addCnt, Attacker suspect found by IP count! Domain = rdpguard.com, ip = 66.152.133.228. Source: over 2 years ago