Feature #1019
closedLagg Failover Mode Master Interface
100%
Description
when creating a lagg interface in failover mode I am not able to choose the master interface.
The first interface in the list becomes the master, which in my case is making
the lagg choosing a 100mbit interface over a 1gbit interface.
An additional drop down menu would be nice.
Updated by Jim Pingle over 12 years ago
- Status changed from New to Rejected
Unfortunately FreeBSD doesn't support setting any such options for lagg.
From lagg (4):
BUGS
There is no way to configure LACP administrative variables, including
system and port priorities. The current implementation always performs
active-mode LACP and uses 0x8000 as system and port priorities.
Updated by Martin Klein over 12 years ago
The above is true for an lagg interface
that is running in LACP mode.
This bug was filed for an lagg interface
that is running failover mode.
example em1 master:
ifconfig lagg0 up laggproto failover laggport em1 laggport em0
example em0 master:
ifconfig lagg0 up laggproto failover laggport em0 laggport em1
So the only thing needed is a interface priority in the web interface
which is observed when calling the ifconfig command.
Updated by Chris Buechler over 12 years ago
- Tracker changed from Bug to Feature
- Status changed from Rejected to New
- Affected Version deleted (
2.0)
that is a legit feature request.
Updated by Christian Ulrich about 8 years ago
Is this on a roadmap for any future release? I just ran into this issue today myself and found this feature request.
Updated by Jim Pingle about 5 years ago
- Category changed from Interfaces to LAGG Interfaces
Updated by Viktor Gurov over 4 years ago
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Viktor Gurov over 4 years ago
- Status changed from Feedback to Resolved
- Target version set to 2.5.0
works as expected on 2.5.0.a.20200403.1936