Project

General

Profile

Actions
Copy link

Feature #12819

closed

GUI option to configure layers for LACP hash

Added by Mat Clarke about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
LAGG Interfaces
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default

Description

Currently when creating an LACP LAG interface it gets created with the hashing "lacp lagghash l2,l3,l4" not all switches support this LACP hashing so would be good to give users the option to configure this when creating LACP interfaces so they could select "Layer 2", "Layer 2 + Layer 3", etc

Related issues

Related to Bug #12831: Typo in in /etc/inc/interfaces.inc line 1107Resolved

Actions
Actions
Copy link
 #1

Updated by Viktor Gurov about 2 years ago

  • Assignee set to Viktor Gurov
Actions
Copy link
 #2

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.7.0
  • Plus Target Version set to 22.05
Actions
Copy link
 #3

Updated by Viktor Gurov about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Ronald Schellberg about 2 years ago

I am getting a syntax error in interfaces.inc at 1107 on boot up that drops pfsense to login prompt.

Are we missing a . in the code after "/sbin/ifconfig"?

mwexec("/sbin/ifconfig " escapeshellarg($laggif) . " laggproto " . escapeshellarg($lagg['proto']) . " {$lacptimeout} {$lagghash}");

The 2022 2/19 6:00 update should be pulled as it brakes installations.

I see it has been fixed via #12831

Actions
Copy link
 #5

Updated by Jim Pingle about 2 years ago

  • Related to Bug #12831: Typo in in /etc/inc/interfaces.inc line 1107 added
Actions
Copy link
 #6

Updated by Jim Pingle about 2 years ago

  • Subject changed from Allow LACP hashing be configured via the pfSense WebGUI to GUI option to configure layers for LACP hash

Updating subject for release notes.

Actions
Copy link
 #7

Updated by Jordan G about 2 years ago

tested on 22.05.a.20220402.0600 options for LAGG now show -
Layer 2/3/4/ (default)
Layer 2 (MAC Address)
Layer 3 (IP Address)
Layer 4 (Port Number)
Layer 2/3 (MAC + IP)
Layer 3/4 (IP + Port)
Layer 2/4 (MAC + Port)

Actions
Copy link
 #8

Updated by Viktor Gurov about 2 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #9

Updated by Jim Pingle about 2 years ago

  • Status changed from Resolved to Feedback

That only showed that the GUI option was there -- It still needs to be tested at the OS level to make sure the selected options are placed on the LAGG, get set at boot, and actually work as expected.

Actions
Copy link
 #10

Updated by Chris Linstruth about 2 years ago

Ran through the various settings. Looks good. All passed basic pings to another host across the lagg.

Layer 2/3/4 (default)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l2,l3,l4
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 2 (MAC Address)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l2
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 3 (IP Address)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l3
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 4 (Port number)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l4
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 2/3 (MAC + IP)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l2,l3
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 3/4 (IP + Port)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l3,l4
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Layer 2/4 (MAC + Port)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l2,l4
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

Back to Layer 2/3/4 (default)
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        laggproto lacp lagghash l2,l3,l4
        laggport: ix2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
Actions
Copy link
 #11

Updated by Chris Linstruth about 2 years ago

While I agree this is a welcome feature addition it should not matter what the other side supports. This is for transmission only. The other side does not have to match and can, in fact, be set differently..

Actions
Copy link
 #12

Updated by Viktor Gurov about 2 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF