this post was submitted on 18 Nov 2024
113 points (97.5% liked)

Selfhosted

40218 readers
1212 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] CarbonatedPastaSauce@lemmy.world 43 points 11 hours ago (4 children)

The only one I haven't seen mentioned here that is a requirement for me is OPNsense. I've been using it for a couple years, and pfSense before that for a very long time. Never going back to commercial routers and their shitty / buggy / backdoored software. I highly recommend OPNsense over pfSense for the UI improvements alone, but there are other reasons to use/support OPNsense over pfSense.

On my network it handles internet firewall, internal firewall, and all routing across 5 VLANs and between two internet gateways. It does 1-1 NAT for my public IPs, inbound VPN, outbound VPN for my *arr stack, and RDNS blocklists with the data source being a script I wrote that merges from several sources and deduplicates the list. It is my internal certificate authority (I don't miss you at all, Windows CA), DHCP for the guest wifi, and does pihole-like ad blocking via DNS for my entire network. And it does all that running in a VM with 2GB of RAM, of which it only uses about 60% on my install.

It is an incredibly powerful tool, not terribly difficult to learn, has a pretty damn good UI for FOSS, and in my opinion is a fantastic foundation for a complex home network / homelab. Unlike pfSense, which corrupted itself twice over the years I ran it, it has never let me down. And every update has been painless over the years.

[–] militaryintelligence@lemmy.world 7 points 4 hours ago (1 children)

I understood some of those words. It make network go?

It make network go very good.

[–] mike_wooskey@lemmy.thewooskeys.com 3 points 6 hours ago (1 children)

I highly recommend OPNsense over pfSense for the UI improvements alone, but there are other reasons to use/support OPNsense over pfSense.

Can you list or summarize some of the other reasons?

Eh, I've forgotten a lot of the details and it's drama that I don't care to relearn about. Easy to find online with some basic searching if you want to read about it.

[–] witx@lemmy.sdf.org 2 points 8 hours ago* (last edited 8 hours ago) (1 children)

How many NICs do you have on your opnsense machine?

It’s a VM so technically none I guess, but my hypervisor hosts have a 4 port gigabit card and a 10 gig fiber card, plus another gigabit port on the motherboard.

OPNsense is using 6 interfaces, 2 WAN and 4 LAN, but it’s all virtualized.

[–] coronach@lemmy.sdf.org 3 points 10 hours ago (1 children)

Second OPNsense. pfSense also is maintained by some pretty shitty individuals.

Yeah I hinted at it but didn’t feel like going into it. It’s why I switched though, and happily I found OPNsense to just be better anyway.