ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
STPLLDP
Network & CoreCore trackIntermediateOSI: Data Link LayerStandard: IEEE 802.1AX

LACP

— Link Aggregation Control Protocol (IEEE 802.1AX)

LACP exchanges control frames between two directly connected devices so they agree on which physical ports belong to the same aggregation group. Once the bundle is formed, traffic is distributed across member links by a hash of the frame headers, and a failed member is removed without breaking the logical link.

Read first: Ethernet (802.3)Content reviewed 2026-11-18

Interactive Session: How LACP Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of LACP.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

Rogue link aggregation member

Interception

A device that speaks LACP can join a link aggregation group and receive a share of the bundled traffic.

Attackersimulated
LACPtarget
Attack step 1 of 3
Negotiate LACP

The attacker sends LACPDUs with a matching aggregation key and system parameters.

What a defender can see

An unexpected port joins an existing port-channel.

Impact if unmitigated

Partial interception of inter-switch traffic.

Defences that matter
  • 802.1X on all access ports
  • Port security and unused-port shutdown
  • Monitor port-channel membership changes

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • LACPDUs sent as Slow Protocol frames with EtherType 0x8809 and subtype 0x01
  • Actor and partner system information with operational keys per port
  • Active and passive modes for controlled negotiation
  • Automatic removal of failed member links from the bundle
  • Per-flow load balancing based on a configurable hash

Real-World Use Cases

  • Switch-to-switch uplinks that need more than one link of bandwidth
  • Server-to-switch bonds for throughput and redundancy
  • Redundant paths that must not be blocked by STP

Advantages & Strengths

  • Increases capacity while keeping a single logical interface
  • Detects miswired or half-configured links and keeps them out of the bundle

Limitations & Vulnerabilities

  • A single traffic flow cannot exceed the bandwidth of one member link
  • Both ends must use compatible hashing or traffic may become unbalanced