FAQ what is lagg

From PFSenseDocs

This article is part of the DEVELOPMENT series. Any features, steps, or general information contained in this article is 100% unsupported and may break your system. Use at your own risk!

Contents 1 Summary 2 pfSense Features 3 Limitations 4 Requested Features

Summary

From the man page

The lagg(4) interface allows aggregation of multiple network as one virtual lagg interface for the purpose of providing fault-tolerance and high-speed links.

It is used for layer-2 Link Aggregation and failover, and supports the EtherChannel (Cisco-propietary) and Link Aggregation Control Protocol (LACP, 802.3ad) protocols.

See also http://nzfug.nz.freebsd.org/nzfug/HandbookUpdates/NetworkAggregation for more details.

pfSense Features

Currently (as of 07/09/2007), HEAD is the only branch that contains any WebGUI modifications that will allow you to create/delete lagg interfaces.

• Supports EtherChannel or LACP Protocols
• Supports 2 or 4 ports in a lagg "bundle".
• Can use 100mb or 1gbit interfaces
• Supports VLAN Trunking (via 802.1q) on lagg ports.
• Tested with Cisco (2 x 2900XL's) and HP (1 x 2524) switches.

Limitations

• Since the lagg interfaces don't allow you to use the underlying NIC's hardware VLAN tagging mechanism, MTU's for VLANs on lagg interfaces will be 1496, to account for the extra VLAN tagging information.

Requested Features

• Let us know!

This article is part of the DEVELOPMENT series. Any features, steps, or general information contained in this article is 100% unsupported and may break your system. Use at your own risk!