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

Do I need to delete my interfaces before creating a LAGG group?

Scheduled Pinned Locked Moved General pfSense Questions
8 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.
  • S
    sofakng
    last edited by Nov 23, 2015, 7:31 PM

    My current pfSense router has two Ethernet ports.  One port was for the cable modem and the other went to a managed switch.

    I'd now like to connect my cable modem to my switch (on a dedicated VLAN), and then create a fault-tolerant LAGG on the two ports on my router to my switch.

    However, do I need to delete all my existing interfaces?  I have a lot of reserved DHCP addresses, etc, that I'd rather not need to recreate.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • ?
      Guest
      last edited by Nov 24, 2015, 2:39 AM

      I have zero networking knowledge, but this don't sound the slightest bit right. To plug your cablemodem into your switch sounds incorrect. Even with your proposed VLAN method.

      Just wanted to save you the headache. You are creating problems for yourself.

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by Nov 24, 2015, 2:45 AM

        Even if you could manage to migrate you interfaces how are you going to administer them? You really need 3 interfaces. You could use wifi(standing by for flak!!).

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by Nov 24, 2015, 3:56 AM

          Seems like just from a latency viewpoint you are introducing 3 extra hops for every internet packet with your VLAN approach..

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by Nov 24, 2015, 4:17 AM

            https://doc.pfsense.org/index.php/Migrate_Assigned_LAN_to_LAGG

            https://forum.pfsense.org/index.php?topic=49713.0

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by Nov 27, 2015, 2:30 AM

              Plus I think that you basically would have your switch "Internet Facing" so any vulnerabilities there could be nasty. VLAN or Not.
              I really wish a network professional would chime in as I am not trained. Maybe your VLAN method is hunky dory. It sounds risky to me. Did you find this method in a how-to or what?

              If its just for experimentation you may be able to get it working.

              That second post from the forum was to show how messed up things can go. The official pfSense instructions look fine, but you will lose all your interface settings. Count on it your first couple of times. Especially if interface 'constrained'.

              1 Reply Last reply Reply Quote 0
              • ?
                Guest
                last edited by Nov 27, 2015, 3:11 AM

                I'd now like to connect my cable modem to my switch (on a dedicated VLAN), and then create a fault-tolerant LAGG on the two ports on my router to my switch.

                And what sense should this make?

                1 Reply Last reply Reply Quote 0
                • D
                  Derelict LAYER 8 Netgate
                  last edited by Nov 27, 2015, 6:53 PM

                  If you want to start messing around with LAGG you'll probably just need to bit the bullet and get more interfaces.

                  Amazing how you start to chew through switch ports and interfaces when you start down this road. I just had to get a 48-port switch for my home/bench. Ran out at 24.

                  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
                  8 out of 8
                  • First post
                    8/8
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received