• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • HybridSarcasm@lemmy.worldMtoSelfhosted@lemmy.worldVLAN question
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    3
    ·
    6 months ago

    With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.


  • HybridSarcasm@lemmy.worldMtoSelfhosted@lemmy.worldVLAN question
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    6 months ago

    If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.

    Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).

    Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.