• 8 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle














  • I did end up setting up my new Protectli appliance today. As i said below, I ended up with OPNsense and I have been able to replicate 97% of pfBlockerNG’s functionality on OPNsense. I’ve been able to load all of my previous DNS blocklists (including my own personal blocklists on Github), set up cron jobs (in the GUI) to update these lists every week and and whitelisted some sites too. The only thing that sucks is that regex isn’t supported. Instead they do wildcard domains (*.ampproject.org). Not nearly as good as regex but it’s better than nothing.

    I also used pfBlockerNG for hardcoded ip address blocks (like Roku hard-coding 8.8.8.8). For that, I used the alias function in the firewall and just set up floating rules for that. Definitely not as convenient as a list, but they don’t change very much. Also, for IP addresses for security, OPNsense has a whole IDS section that pfBlockerNG used to handle.

    pfBlockerNG made everything clean and easy but I’ve been able to get 97% of the functionality in pfBlockerNG in OPNsense. The 3% deficit is lack of regex support.






  • Your sorting is working properly. When you sort by active, you’ll get posts that people are actively commenting on. When you sort by hot, you’ll get posts that lots of people are looking at, and when you sort by new, well, those are the new posts… so 10 seconds seems about right.

    It works the same on Reddit. It’s just that there’s a lot more users, a lot more engagement and a lot more overall content over there.