CFT: new trunk(4)
Lars Erik Gullerud
lerik at nolink.net
Mon Apr 16 07:07:58 UTC 2007
On Sun, 15 Apr 2007, Shteryana Shopova wrote:
> LACP == Link Aggregation Control Protocol - dynamic trunking - one of
> the modes trunk(4) supports. And it's Cisco vs the rest of the world
> where Cisco calls a trunk multiple VLANs over single physical
> interface and the rest of the world calls a trunk multiple physical
> interafces bundled together. We don't have to necessarily agree with
> Cisco. Please keep the current name.
I beg to differ. The terms "trunk" and "trunk-style link" are used
throughout IEEE 802.1Q-2005 in examples and illustrations to demonstrate
the concept of carrying multiple tagged vlans over a single link, as
opposed to an "access-style link" carrying a single untagged vlan.
(802 standards that are more than 12 months old are available for free
download at http://standards.ieee.org/getieee802/ )
As for "the rest of the world":
In the telecoms industry, the term "trunk" is also generally used to
indicate one datalink carrying multiple signal streams, an example would
be an E1 link carrying n * 64kbit voice channels.
In the carrier ethernet/metro ethernet space, the term "trunk" is also
generally used in what you would call "cisco-style". Most equipment
vendors do also agree with cisco there, with Extreme being one of the
notable vendors on the other side. (Alcatel, Riverstone etc. uses trunk
in the vlan trunk sense).
However in the end, whether Cisco or Extreme are in the right, is really
not that interesting. The point is really that the name IS used for
different features, and that it therefore IS confusing for users. So why
not just give it a name that is more indicative of what the feature
While the OpenBSD guys have given us a lot of great stuff, the name
"trunk" for this interface is not among them (although the interface
I'd tend to prefer bond(4) so Linux users will feel familiar, although
aggr(4) would be equally good.
More information about the freebsd-current