Hmm I think I this does not work in case you meant to put the bridge as the parent of the VLANs, OPNsense does not allow this:
now, define 3 vlan with the vlan tags you defined in the switch + ap, you need to say that the port they are received is the bridged port
However I think I found another solution that works exactly as I want but it is very weird so be warned:
- Created
vlan01.11andvlan02.11onigc1andigc2respectively, assigned them, enabled them and gave each a static ipv4 (192.168.11.1and192.168.11.2) - Created a bridge with both VLANs as members, did NOT assign and enable this (when I do the setup breaks (?!))
- Use KEA DHCP instead of ISC:
- In settings listen on both VLAN interfaces
- In subnets create the subnet with
subnet=192.168.11.1/24and a pool of192.168.11.21-192.168.11.254, uncheck “Match Client-id” and “Auto collect option data” and set Routers, DNS and NTP Servers to192.168.11.1and192.168.11.2
This way KEA will give out IP addresses on all interfaces with a static IP in the defined subnet. Make sure to disable ISC DHCP as it otherwise caused issues with KEA and somehow also Unbound (I also enabled “Register ISC DHCP4 Leases” in Unbounds settings because I had weird issues with SERVFAIL there).
I repeated this process for the vlan0x.13 and vlan0x.14. Now internet access works on all VLAN interfaces, aswell as the normal interfaces and I can still define Rules for each VLAN.
What I don’t get about this is why I cannot assign or enable the bridge interface… but I guess it works soo I’m happy. Thank you for your suggestion though!








What I would like to see is a Windows challenge, where they try to achieve privacy as close to out of the box linux as they can get. That would probably genuinely be entertaining.