Fail2Ban VS pfSense

now some things you need to think about: - cloud init - this will need to be secure so lock it down hard anything not needed an alternative OS to look at if you have the ability's is https://www.alpinelinux.org/ also as these devices are not that powerfull every extra agent / abstaction layer you add impacts performance need to look at low over head security https://www.crowdsec.net/ and https://github.com/fail2ban/fail2ban (if you call fail2ban security) - using certificates to authenticate ssh login

See https://github.com/fail2ban/fail2ban for beginner's guide, basically you set it up to monitor logfiles and it would act accordingly (plenty of built-in config to handle various daemons so you don't have to write yourself).

- Nginx & crowdsec/fail2ban if you are exposing your parts (services) to the public ( https://hub.docker.com/r/baudneo/nginx-proxy-manager, https://www.crowdsec.net, https://www.fail2ban.org )

— In /etc/fail2ban/action.d/cloudflare.conf I copied the file from https://github.com/fail2ban/fail2ban/blob/master/config/action.d/cloudflare.confand added my ‘cftoken’ and ‘cfuser’ on the bottom

https://github.com/fail2ban/fail2ban is a mature, easy to set up way to have some dynamic firewall rules that respond to attacks. There are more sophisticated options, but they are probably not worth the return on time investment for you.

You can create your own regexes for custom services: https://github.com/fail2ban/fail2ban/wiki/Developing-Regex-in-Fail2ban

Others seem to be (or were) experiencing this too: https://github.com/fail2ban/fail2ban/issues/3100

One option is Firewalla Gold Plus, or you could buy a mini PC like it and run pfSense/OPNsense yourself.

Download and install pfsense as a virtual machine or partition: https://www.pfsense.org Configure it with the rules you want: https://youtu.be/VAGFGppSt74 Play with it, but be careful because it will block all traffic unless you check everything properly.

Another option is Firewalla, or buy a mini PC like it and run pfSense/OPNsense yourself. Two similar concepts, with the cost being either money or your DIY time. A lot of Firewalla users say that it's much easier for home use than pfSense/OPNsense, so you might find it worthwhile to spend a little more on it upfront and have to tinker less.

If you want firewall, I think you can use https://www.pfsense.org/ or https://opnsense.org/ , maybe running on an old PC or a Raspberry Pi. Not sure.

I've recently started using OPNsense. It's similar to pfSense, but seems to be considered a little more user-friendly.

For most router issues, I recommend people always put them in to dumb bridge mode and put a proper firewall like pfsense or opnsense as your gateway.

I have found that my historical average packet loss is about 0.02%. Something distinctly changed around 4/20 of this year, and now the average packet loss has gone up to 0.05% with spikes even higher, associated with periods of elevated ping times. It rarely did that before. Typically the IPv6 stack has more problems than v4 (especially an incident of packet loss on 4/28), and neither has been trouble-free since I started service in early 2020. My data comes from a pfSense installation.

I have done this using the Pfsense