• 6 Posts
  • 20 Comments
Joined 3 years ago
cake
Cake day: June 21st, 2023

help-circle
  • You are me, 3 years ago! I’m diagnosed with ADHD and what you described is exactly how I felt when I was starting out. I even bought a RaspberryPi 4B+ CanaKit which sat in the box for over a year, just like you.

    3 years later I have the Pihole, OPNsense router & firewall, Jellyfin, Traefik reverse proxy, and a bunch of other stuff too. My advice would be to start super small so you don’t feel overwhelmed. It is incredibly easy to get overwhelmed with all of this.

    For what it’s worth, before I started hosting anything, I started with NextDNS. I just set up my iPhone and computers (then mac, now mostly linux) to use that service. It comes with super easy-to-use instructions and you can start for free. If you don’t like it, you can always just delete the account and it’ll be like you never used it at all. Very low risk but doing this will teach you about DNS. From there you can begin to move to a Pihole and Docker, if you’re comfortable.

    Feel free to DM if you want. It’s a great community here and we’re all a pretty relaxed group.


  • I can’t even specify the allowed IPs for a connection

    Funny. This was the exact use case which cemented my pf/OPN sense decision. I used to use pf, now use OPNsense. And as you probably know, the IP specificity issue is not just regarding Wireguard, it’s also regarding your reverse proxy, if you’re running one.

    As an aside, I have OPNsense handling DHCP which broadcasts two PiHoles (redundancy) as the DNS to my networked machines/devices. Then for upstream DNS, I have those two piholes pointed at a dedicated technitium dns box – it’s it’s an authoritative dns server, not just a recursive one like unbound. As I said in my previous comment, there are probably better or fancier setups but this one, for my needs, is sufficient.























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

    Edit: I saw the article you were referring to. That’s how I set up IP blocking. But Unbound in OPNSense supports blocklists (it’s even called DNSBL) and that is much easier/quicker to set up than using aliases IMO. Just make sure you toggle on Advanced Mode. That’s how you quickly load the custom blocklist urls. Just remember to seperate the urls with a comma. I forgot the first time and nothing worked.