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

    LACP Hashing

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    5 Posts 3 Posters 784 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.
    • M
      MrClayPole
      last edited by

      I have pfSense 2.6.0 connected to a switch via a 2 port LACP. The switch has a global setting for all LACP hashing which I would like to set to Layer 2 only. I can see from the interfaces section in pfSense however that it's using "lacp lagghash l2,l3,l4" is it possible to change it to L2 only?

      1 Reply Last reply Reply Quote 0
      • viktor_gV
        viktor_g Netgate
        last edited by

        Please create a feature request:
        https://docs.netgate.com/pfsense/en/latest/development/system-patches.html

        1 Reply Last reply Reply Quote 0
        • M
          MrClayPole
          last edited by

          Thanks, I've made the feature request https://redmine.pfsense.org/issues/12819

          Is there any way to configure the LACP hashing via the console?

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

            @mrclaypole I see your redmine and agree it would be nice to have that granularity.

            Please keep in mind that the hashing method is only for transmitted frames. The frames can arrive on any port in the aggregation at any time and the sending algorithms can be different on each side.

            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
            • M
              MrClayPole
              last edited by

              I've done some more reading since my first post and I had mistakenly thought that they need to match or "bad things would happen". Thanks for clarifying.

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