this post was submitted on 15 Nov 2023
2 points (75.0% liked)
Homelab
371 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 11 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Your extensive config is probably your issue and not opnsense. You said you've been running it for a few years but seemingly 4 months ago, you couldn't figure out a basic rule to block internet for a single ip.
I second this. No offense to OP!
I never noticed any "slowing down issues" since any of the recent updates. Running OPNsense with a similiar setup to yours "vlans, plugins, policies, suricata, VPN, routes, gateways, HAProxy, etc". Again no issues on 8+ sites, including SiteToSite WireGuard VPNs and with large corporate networks. Some systems running perfectly stable and performant since version 20.x (installed) and now running the latest update.
Therefore I highly think your issues are user error / misconfiguration. Yet, I don't mean to judge but it seems to me that you switching to pfSense will just bring your OPNsense issues with it.
I can't tell how much experience you have with networking/firewalls in general but a lack of that won't bring you any further by switching to pfSense.