Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    VLANs Across Multiple Interfaces

    Scheduled Pinned Locked Moved Routing and Multi WAN
    4 Posts 2 Posters 4.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • superweaselS
      superweasel
      last edited by

      Here is a problem I have been struggling with:

      WAN: PPPoE
      LAN: igb0
      OPT1: igb2

      VLAN 10 -> igb0, 10.0.10.0/24
      VLAN 20 -> igb0, 10.0.20.0/24
      VLAN 30 -> igb2, 10.0.30.0/24
      VLAN 40 -> igb2, 10.0.40.0/24
      VLAN 50 -> igb2, 10.0.50.0/24

      802.1Q Switches-
        Switch 1 (SW1): port 1 is connected to igb0 (trunk)
          Port 2: VLAN 20
          Ports 3-5: VLAN 30

      Switch 2 (SW2): port 1 is connected to igb2 (trunk)
          Ports 2-4: VLAN 20
          Ports 4-5: VLAN 40
          Ports 6-8: VLAN 50

      Is it possible to connect a device to SW2, port 4, have it have receive a DHCP address for VLAN 20 and be routable to other VLANs and the WAN? Or to put this another way, can pfSense trunk VLANs across interfaces?

      If so, how do you go about setting this up in pfSense?

      Thanks in advance

      pfSense rig: pfSense SG-4860/120GB SSD
      WAN: CenturyLink Gigabit Fiber

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        VLANs are VLANs.

        Interfaces > (assign) VLAN tab
        Interfaces > (assign)

        VLANs look like discrete interfaces to pfSense.  When you assign an interface to a VLAN it egresses pfSense tagged on the parent interface.  Received traffic tagged with the VLAN is presented to the same interface.

        ![Screen Shot 2015-05-30 at 3.32.39 PM.png](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.32.39 PM.png)
        ![Screen Shot 2015-05-30 at 3.32.39 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.32.39 PM.png_thumb)
        ![Screen Shot 2015-05-30 at 3.32.56 PM.png](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.32.56 PM.png)
        ![Screen Shot 2015-05-30 at 3.32.56 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.32.56 PM.png_thumb)
        ![Screen Shot 2015-05-30 at 3.41.01 PM.png](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.41.01 PM.png)
        ![Screen Shot 2015-05-30 at 3.41.01 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-05-30 at 3.41.01 PM.png_thumb)

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • superweaselS
          superweasel
          last edited by

          Thanks for the reply.

          I have attempted your setup, with all VLANs assigned to a single interface, in your example em0. This works fine, and you can route between VLANs on that interface. However, it appears VLANs are not trunked to other physical interfaces within pfSense, e.g. VLAN 10 is assigned to physical interface 0 in pfSense, switch with VLAN 10 assigned to some ports is physically connected to interface 1 which is not the assigned interface for VLAN 10 in pfSense.

          If there is a way to make this work, I would greatly appreciate some setup detail or if not that would great to know as well.

          Thanks

          pfSense rig: pfSense SG-4860/120GB SSD
          WAN: CenturyLink Gigabit Fiber

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            pfSense is not a switch.  Your switch is a switch.

            Not sure what you're trying to do but whatever it is, it's beginning to sound like you're doing it wrong.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.