Hi! I’m currently trying to set up my network as seen in the image. USER VLAN has the tag 11, IOT VLAN has the tag 13 and GUEST VLAN has the tag 14. These are tagged by an Omada AP and Omada Switch on individual ports.

So far I have:

  • Assigned igc1 (LAN) and igc2 (Wifi) and enabled them (no IP configured).

  • Created a Bridge between igc1 and igc2 so they are in the same subnet, which I think of as some sort of management subnet.

  • Configured a static IP (192.168.10.1/24) on this Bridge and enabled DHCP. All devices are reachable here and it is also possible to reach the internet from the Omada devices.

  • Created VLANs vlan01.11, vlan01.13, vlan01.14 with their parent being igc1 (Omada Switch).

  • Created VLANs vlan02.11, vlan02.13, vlan02.14 with their parent being igc2 (Omada AP)

  • Assigned all of them and enabled them (no IP configured)

  • Created a Bridge between each pair (vlan01.11 + vlan02.11 etc.)

Now my problem is that seemingly no matter what I do some devices on the VLANs cannot reach the internet because they cannot reach their Gateway.

I tried:

  • Configuring a static IP to the VLAN Bridge (192.168.11.1 for USER VLAN) and enabling DHCP on it with the correct subnet. Doing so not a single device was able to reach the Gateway, but they were able to talk to each other. DHCP worked this way for both endpoints.
  • Instead of configuring a static IP to the VLAN Bridge I configured it right on the vlan02.11 interface and enabled DHCP there. Doing so only the devices on the wifi are able to reach the Gateway but the devices connected via the Switch cannot. In addition DHCP does also not work for devices on the Switch.

Does anyone here maybe have a hint on what I am doing wrong?

Edit: I also tried:

  • Combinations of net.link.bridge.pfil_member and net.link.bridge.pfil_bridge but that didnt work either.
  • Removing the bridge and using only the vlans but with the same subnet
  • thelittleblackbird@lemmy.worldEnglish
    2·
    2 months ago

    Yes, thanks

    The setup seems possible with the exception of all of them under the same subnet. I really discourage it because I am not sure how opnsense and the DHCP sever will work with firewall rules based on ports and not subnetworks. If you accept this deviations what you need to do is:

    • take both ETH ports in the opnsense make a bridge between them
    • 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
    • now define 3 different interfaces (1 per vlan definition)
    • configure every interface with a static ipv4 ip and a different dhcp server, they should have different networks
    • now in the firewall configure how 3 interfaces should communicate to each other

    As. Summary the steps should be

    Briged port -> vlan ether ports -> interface definition -> ipv4 + dhcp configuration -> firewall definition.

    For ipv6 it is almost the same

    • sekki@lemmy.worldOPEnglish
      1·
      2 months ago

      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.11 and vlan02.11 on igc1 and igc2 respectively, assigned them, enabled them and gave each a static ipv4 (192.168.11.1 and 192.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/24 and a pool of 192.168.11.21-192.168.11.254, uncheck “Match Client-id” and “Auto collect option data” and set Routers, DNS and NTP Servers to 192.168.11.1 and 192.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!

      • thelittleblackbird@lemmy.worldEnglish
        2·
        2 months ago

        Congrats if it is working, as far as I know when you do a bridging you shouldn’t have an ip, because both ports are seen as a same Mac interface…

        Something is not working as I think it should. But if it is working nothing else to discuss