summaryrefslogtreecommitdiffstats
path: root/share/man/man4/lagg.4
Commit message (Collapse)AuthorAgeFilesLines
* - Propagate the largest set of interface capabilities supported by all laggthompsa2007-07-301-0/+3
| | | | | | | | | | | ports to the lagg interface. - Use the MTU from the first interface as the lagg MTU, all extra interfaces must be the same. This fixes using a lagg interface for a vlan or enabling jumbo frames, etc. Approved by: re (kensmith) MFC After: 3 days
* Bump date for the previous revision and the driver renaming.brueffer2007-04-171-1/+1
|
* To avoid confusion, mention that the driver was originally called trunkbrueffer2007-04-171-1/+3
| | | | in OpenBSD.
* Rename the trunk(4) driver to lagg(4) as it is too similar to vlan trunking.thompsa2007-04-171-0/+172
The name trunk is misused as the networking term trunk means carrying multiple VLANs over a single connection. The IEEE standard for link aggregation (802.3 section 3) does not talk about 'trunk' at all while it is used throughout IEEE 802.1Q in describing vlans. The lagg(4) driver provides link aggregation, failover and fault tolerance. Discussed on: current@
OpenPOWER on IntegriCloud