Comment on Help configuring OPNsense VLANs? Tutorials I find seem to quickly become outdated.
CoreLabJoe@piefed.ca 5 days agoThis 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.
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 5 days 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.
35DxwkWn6y7H2SQ.webp
I won’t be able to try this until at least tomorrow after work, more than 24 hours from now, but yes, this was what was in my tutorials as standard. But also agreed in those tutorials was that what I tried doing was even more permissive and ought to “just work”, at the risk of security and with no separation; I always try to do “Hello World” before I try to implement anything of value, and right now I’m barely seeing “Hello”.