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

    Single VLAN existing on Multipule interfaces?

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 3 Posters 1.1k 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.
    • F
      finlstrm
      last edited by

      Ok so heres the scoop.

      I have 2 Cisco 2950's (i know old, please don't laugh. They were free and they work  :)) I have all my VLANs configured on both switches [7,10,11,37,100]. I also have these VLANs defined on my PFSense router (Stephew10 FTW on my firebox]. I have this setup working fine with one switch and a single 2 port LAGG.

      I'd like to take my second switch, setup a second LAGG on the router, then also have all of my VLANs exists on both interfaces so that all VLANs can be accessed and used on both switches.

      I've done a bit of research, but I cannot find if anyone has even done something like this… Is this even possible?

      Thanks,

      Hardware: Watchguard Firebox x1250e

      Is this a normal bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?

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

        Use switch trunk ports to trunk VLANs between switches, not router ports.

        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
        • F
          finlstrm
          last edited by

          I know i can get a working configuration, with all my VLans existing on all switches, by doing the following:

          Router - msk2,msk3 - LACP Lagged Trunk
            |
            |–- Switch 1 [Ports 23/24 Connected to msk2,msk3 on the router, and ports 21/22 to extend the LAGG to another switch]
                      |
                      |–- Switch 2 [Ports 23/24 connected to 21/22 on switch 1]

          However the configuration I'm looking for is as follows:

          Router [msk0.msk1 - LAGG1] [msk2,msk3 - LAGG0] both LACP Trunks
                          |                                            |
                          |–- Switch 1                        |--- Switch 2

          And still have my Vlans exist on both switches....

          Or can I create a single 4 port LAGG [msk0-3] and connect 2 ports of the LAGG to each switch? ie:

          Router [msk0-3] LACP LAGG
                |        |
                |        |–-Switch 2 [ports 23/24 connected to msk2/3]
                |–-Switch 1 [ports 23/24 connected to msk0/1]

          or am what I am asking simply impossible?

          Hardware: Watchguard Firebox x1250e

          Is this a normal bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?

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

            Router [msk0.msk1 - LAGG1] [msk2,msk3 - LAGG0] both LACP Trunks
                            |                                            |
                            |–- Switch 1                        |--- Switch 2

            Why on Earth would you want to do that?  Use a switch.

            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
            • jahonixJ
              jahonix
              last edited by

              A router is not a switch. Bridging interfaces tries to make it a switch but never succeeds.
              This has been discussed in all possible (and quite some impossible) configurations already.

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