Thanks for letting me know! Glad it worked out in the end...
Yes my OPNsense guides need a bit of a re-write and more logical structure I think; I've received a lot of great feedback on them I need to incorporate.
Enjoy your new firewall ;)
Thanks for letting me know! Glad it worked out in the end...
Yes my OPNsense guides need a bit of a re-write and more logical structure I think; I've received a lot of great feedback on them I need to incorporate.
Enjoy your new firewall ;)
If you knew what was under the hood you would not say it's "just" customized nginx... It's more like customised, optimized and simplified.
It has many enhancements builtin like automatic certificate generation and renewal, fail2ban, prebuilt optimized configs, and easily enhanced security with crowdsec and even geofencing.
But made way easier than doing that separately with raw NGINX.
It's much more friendly to pickup and run with then raw NGINX.
It can be done, just carefully. You can definitely accidentally block yourself out if you set a firewall rule up incorrectly, or in higher precedence of order for example. OPNsense (like almost every firewall known) processes rules in a "top down" order. So you put your blocks at the bottom!!!
Reverse proxy won't lock you out, essentially that's just slapping HTTPS on a webserver/service like Jellyfin, so you can access it without requiring a VPN.
Here's a reverse proxy explainer, pt 2 is the actual setup!
No worries, hope it helps, let me know if you have questions =)
Never heard of Rayfish but just googled, it's a mesh VPN so probably wouldn't want to push that through a reverse proxy to authelia, it would just slow it down....
I personally use wireguard as my VPN, not tailscale or headscale or any of that but I do understand some people need something that can get around CGNAT or other issues.
What you could try is an inverse sense of match rule, which by default, allows access to the internet but not to other VLANs. This is what I do and is the standard I think that should be the default!
If you read the LAN rules at the link there, it basically has you setup RFC1918 IP space as an alias, and then setup an inverse option the logic is:
Anything that is NOT Private IP space - ALLOW!
So outbound from that vlan/network/subnet to internet --> Allowed!
Then you make separate rules to actually allow whichever VLAN access to the other, that you want.

Thank you for taking a peek!
Let me know if there's something you're looking for. The search function isn't to bad but sometimes the posts can get buried a bit ;)
Oh hello there fellow Canadian blogger! I'm just down the road from you in between Toronto and Montreal (right in the middle actually!)...
I run a tech blog as well, but different focus than yours mostly on c omplete self-hosting, infrastructure and cybersecurity, and media servers.
**We should make some backlinks at some point! **
PS> This site is built off Ghost CMS.
This may help as well, and bridges the gap for some with all the changes from v25.x to v26.x.
Core Lab OPNsense upgrade guide
Your rule looks correct at first glance, but I'll take a peek further. You do need a DHCP pool setup PER VLAN though, so there's that as well.
I use SWAG reverse proxy for this, with Cloudflare for DNS.
Anything that I publicly expose, I have protected with multiple layers up and down my entire stack...
I'm late to the party, but feel my guides can help. I am biased towards them because I wrote them! ;)
It's up to date for v26.x with OPN, that said these guides (3 part series) do need a bit of an overhaul but it does cover VLANs, LAGG/Trunks, DNSmasque and DHCP for each VLAN, with pictures etc...