Shorewall VS SSHGuard

All mentioned items have side-channel borked firewall and route rules in the past. Some bugs intermittently silently block local daemon instances from (re)loading like magic (some bugs only happen when the system is brought up). If your daily tasks include something less borked, than consider yourself very lucky you live without systemd. If I recall, ufw was intended for simple workstation rule sets. Personally,... - Source: Hacker News / 9 months ago

I've been using Shorewall for the last decade or so on everything from custom OpenWRT firewall/gateway solutions to servers running Debian or Ubuntu. It's great software that makes managing iptables/netfilter a breeze. Alas after many years, Mr. Eastep has retired and it doesn't appear the project is maintained by a new person or team. Source: about 1 year ago

Shorewall (https://shorewall.org/) can do the job easily. Source: over 1 year ago

Despite administrating Linux machines since 1994, I have never really looked closely at iptables because I was using shorewall and the briefly firehol. Source: over 1 year ago

You should just use https://shorewall.org/. Source: almost 3 years ago

There are now better defensive tools (I use https://sshguard.net/); not that there are any accounts on this system that are vulnerable, but it does keep the relevant logfile from growing to astronomical size. Source: about 3 years ago