Thanks, I’m going to have to go through this with a fine-toothed comb to see where I went wrong. If you read my other comments and have a hunch as to the problem in the meantime, I’m all ears, lol.
Comment on Help configuring OPNsense VLANs? Tutorials I find seem to quickly become outdated.
CoreLabJoe@piefed.ca 1 week ago
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…
ampersandrew@lemmy.world 1 week ago CoreLabJoe@piefed.ca 1 week ago
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.
- ampersandrew@lemmy.world 1 week ago
They’re on different subnets, so I figured. I believe DHCP is set up properly, because it assigned an IP to that mini PC in my specified range.
CoreLabJoe@piefed.ca 1 week ago
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.
Hey, just wanted to chime in and say thank you. I think your guide moves a little fast for someone like me, but through omission, I was able to suss out what was wrong, I think. I don’t know if it was a default setting or if it was something I picked up without understanding it while trying to fill in the gaps of DNSmasque DHCP, but I had two DHCP Options set; one was a Set option for router[3], and the other was a Set option for dns-server[6]. The fact that you didn’t have that in your guide at all led me to try a configuration without them, and now I’ve got full connectivity on my VLAN. I’ll of course now start properly blocking access off rather than leaving everything totally permissive before opening up services to the web.