AGGR(4)
β¨ AGGR(4) β¨
okay so bestie, welcome to aggr, the IEEE 802.1AX Link Aggregation (LACP) network interface β and yes it's a kernel interfaces manual page, we're getting technical today and honestly? it's giving iconic π
π NAME π
aggr β the IEEE 802.1AX Link Aggregation (LACP) network interface. that's her. that's the whole name. periodt π
πΈ SYNOPSIS πΈ
pseudo-device aggr
literally one line and she's already serving β¨
π¦ DESCRIPTION π¦
so the aggr driver implements IEEE 802.1AX (which used to be called 802.3ad back in the day, glow-up era) Link Aggregation, and what that does is combine one or more Ethernet interfaces into a single logical interface. one interface to rule them all, no cap π
the Link Aggregation Control Protocol (LACP) is what negotiates the aggregation of the member interfaces with a partner device. she's a negotiator, she's a diplomat, she's doing the most π«Ά
aggr interfaces have to be configured to use one or more Ethernet interfaces as ports, and they talk to a partner device over those ports using LACP. member interfaces that successfully negotiate with a partner device get aggregated into a single logical link β congrats to them honestly π. packets transmitted through an aggr interface pick an aggregated interface for transmission, and packets received by an aggregated device appear to be received by the aggr interface it is a member of. the vibes are seamless, the packets are confused about where they came from, we love that for them π
you can create aggr interfaces at runtime with the ifconfig aggrN create command, or by setting up a hostname.if(5) configuration file for netstart(8). the interface itself gets configured with ifconfig(8) β go read its manual page for more info, iykyk π
a random MAC address gets generated when an aggr interface is created β¨. if you want a specific one instead, assign it with the ifconfig(8) command lladdr etheraddr. main character MAC energy, your choice π
also real quick: other forms of aggregation of Ethernet interfaces exist, and they're available using the trunk(4) driver. different driver, different vibe, she's over there if you want her π
π EXAMPLES π
creating an aggr virtual interface on top of two physical interfaces β watch and learn bestie:
# ifconfig aggr0 create
# ifconfig aggr0 trunkport em0
# ifconfig aggr0 trunkport em1
# ifconfig aggr0 10.1.1.100/24
# ifconfig aggr0 up
that's it. that's the whole ritual. five lines and she's UP π₯
π§ SEE ALSO π§
go read them. all of them. bestie homework πβ¨
β STANDARDS β
IEEE 802.1AX Link Aggregation. that's the standard. she conforms. she's certified. π
π HISTORY π
the aggr driver first appeared in OpenBSD 6.6. a debut. a moment. we remember π
okay that's the whole page bestie, no notes π
and a little sign-off from the folks who made this page: it's from Debian, dated March 17, 2026, and it's filed under AGGR(4). mwah π«ΆπΈ
π¦ where this page comes from
- nixpkgs unstable: cvs-export
- Copyright (c) 2019 David Gwynne <dlg@openbsd.org>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms