What is IEEE 802.1AE MACsec and how does it achieve line-rate encryption at Layer 2 without CPU latency penalty?

IEEE 802.1AE MACsec (Media Access Control Security) operates at Layer 2 of the OSI stack, directly above the Ethernet physical layer (PHY). MACsec encrypts and authenticates every Ethernet frame traversing point-to-point physical links (such as dark fiber between datacenters, WAN connections, or top-of-rack switch interlinks) using GCM-AES-128 or GCM-AES-256 (with optional XPN 64-bit Extended Packet Numbering). Because MACsec operates below the IP stack, it encrypts all Layer 3 protocols transparently—including IPv4, IPv6, ARP, DHCP, LLDP, and routing protocols (BGP, OSPF)—protecting against rogue switch injection, fiber tapping, and man-in-the-middle sniffing. High-end Network Interface Cards (NICs, such as Mellanox ConnectX-6/7 or Intel E810) and optical transceivers integrate hardware MACsec PHY engines that encrypt frames inline at full 100G/400Gbps line rates with sub-microsecond latency and 0% host CPU utilization.

How is a MACsec Ethernet frame constructed and what information does the 16-byte SecTAG header convey?

When an Ethernet frame is encrypted by MACsec, the original 802.3 Destination and Source MAC addresses are preserved in the clear to enable physical switch forwarding. Immediately following the Source MAC, MACsec inserts an 8-to-16 byte Security Tag (SecTAG) carrying: (1) MACsec EtherType (0x88E5); (2) TCI/AN byte (Tag Control Information and 2-bit Association Number identifying the active Security Association key); (3) SL byte (Short Length indicator for frames under 48 bytes); (4) Packet Number (PN: 32-bit counter for anti-replay defense); (5) Optional 8-byte SCI (Secure Channel Identifier: system MAC address + 16-bit Port ID). The original payload and EtherType are encrypted using AES-GCM. Finally, a 16-byte ICV (Integrity Check Value) authentication tag is appended at the end of the frame, followed by the standard 4-byte Ethernet Frame Check Sequence (FCS).

What is the architectural difference between IPsec Tunnel Mode and IPsec Transport Mode?

IPsec Encapsulating Security Payload (ESP, IP protocol 50) operates at Layer 3 and supports two operational modes: (1) Transport Mode: Encrypts only the Layer 4 payload (TCP/UDP) and upper-layer data. The original IP header is preserved and remains visible to intermediate routers. Transport mode is designed for host-to-host communications where both endpoints understand IPsec. It incurs smaller packet overhead (typically ~38 to 46 bytes) but leaks the internal host IP addresses to the network; (2) Tunnel Mode: Encapsulates the ENTIRE original IP packet (header + payload) inside an entirely new outer IP header. Tunnel mode is mandatory for Site-to-Site VPN gateways (connecting two remote private LAN subnets over the public internet) and Roadwarrior VPN clients. Because the internal private IP addresses (e.g. 10.0.0.0/8) are encrypted inside the ESP payload, intermediate internet routers only see the outer public gateway IP addresses.

How does the Linux XFRM (Transform) framework manage Security Associations (SA) and Security Policies (SP)?

In Linux, IPsec is implemented natively in the kernel via the XFRM framework. XFRM maintains two distinct in-kernel databases: (1) Security Policy Database (SPD): Configured via "ip xfrm policy", the SPD defines which traffic must be encrypted or decrypted based on selectors (source subnet, destination subnet, protocol, port). When an outgoing packet matches an "action allow dir out tmpl" policy, the kernel intercepts it and redirects it to the transformation engine; (2) Security Association Database (SAD): Configured via "ip xfrm state", the SAD stores the active cryptographic parameters: Security Parameter Index (SPI), cryptographic cipher (e.g. aead rfc4106(gcm(aes)) 256), encryption key, and replay window settings. User-space IKEv2 daemons (StrongSwan, Libreswan) negotiate keys via Diffie-Hellman and dynamically program the kernel XFRM state via Netlink (XFRM_MSG_NEWSA/NEWPOLICY).

Why is NAT Traversal (NAT-T / UDP Encapsulation port 4500) required for IPsec ESP in residential or cloud environments?

Raw IPsec ESP packets use IP protocol number 50 without any Layer 4 TCP or UDP port numbers. Standard Network Address Translation (NAT) routers (such as home Wi-Fi gateways or cloud NAT gateways) rely on Layer 4 port multiplexing (NAPT/PAT) to map private client sockets to a single public IP. When raw ESP packets traverse a NAT router, the router cannot track socket states and drops incoming return packets. Furthermore, if the packet uses Authentication Header (AH), modifying the IP header invalidates the cryptographic checksum. NAT Traversal (NAT-T, RFC 3948) solves this by encapsulating the entire ESP packet inside a UDP packet on port 4500. During the IKEv2 phase 1 negotiation on port 500, endpoints detect the presence of intermediate NAT devices (via NAT-D payloads) and automatically switch subsequent traffic to UDP port 4500.

How does Hardware Cryptographic Offload (XFRM offload / Inline NIC offload) compare between software crypto, lookaside crypto, and inline NIC crypto?

There are three levels of IPsec/MACsec cryptographic processing: (1) Software CPU Crypto: The host CPU executes AES-NI and PCLMULQDQ instructions. While fast (~2-4 GB/s per core), processing 100 Gbps requires 5 to 10 dedicated CPU cores and introduces memory bus contention; (2) Lookaside Accelerator (e.g. Intel QAT PCIe card): The kernel DMA-transfers packets from host RAM to an accelerator card, which encrypts them and DMA-transfers them back to RAM before transmission. While offloading CPU math, lookaside accelerators double PCIe bus traffic; (3) Inline Hardware Offload (e.g. Mellanox Innova / ConnectX-6 Dx): The NIC hardware contains an inline AES-GCM ASIC directly in the network data path. Plaintext packets are pushed once to the NIC tx-ring; the NIC encrypts them on-the-fly as they serialize onto the physical optical cable. This achieves zero CPU utilization, zero extra PCIe copies, and true line-rate 100 Gbps performance.

MACsec (802.1AE), IPsec (ESP/IKEv2) & Hardware Layer Encryption Studio

Verified Specification | Standardized Formulas | Instant Precision

Secure & Private (Zero Data Retention) Free Access • No Sign-Up

IEEE 802.1AE MACsec RFC 4303 IPsec ESP Linux XFRM Engine Hardware Crypto Offload

MACsec (802.1AE), IPsec & Hardware Layer Encryption Studio

Simulate Layer 2 IEEE 802.1AE MACsec frame encapsulation with SecTAG headers, model Layer 3 IPsec ESP tunnel vs transport mode packet dissection, inspect Linux XFRM state and policy rules, and calculate hardware crypto offload line-rate throughput.

100% Client-Side Engine

MACsec Interface Configuration

Cipher Suite

Secure Channel Identifier (SCI Inclusion)

Payload Size (Ethernet MTU bytes)

1,500 B

SecTAG Frame Breakdown & Encapsulation Overhead

MACsec Header Overhead

32 Bytes

SecTAG (16B) + ICV (16B)

Line-Rate Efficiency (1500 MTU)

97.9%

Useful payload bandwidth

IPsec Encapsulation Parameters

IPsec Mode

NAT Traversal (NAT-T / UDP 4500)

AEAD Cipher Suite

Packet Layer Dissector & Wire Layout

Total Encapsulation Overhead

56 Bytes

Outer IP + UDP + ESP + ICV

Effective MTU (from 1500)

1,444 Bytes

Prevents packet fragmentation

Linux Kernel XFRM Architecture (SAD vs SPD)

Component	Security Policy Database (SPD)	Security Association Database (SAD)
Kernel Object	`struct xfrm_policy`	`struct xfrm_state`
Purpose	Determines WHAT traffic to encrypt or drop	Determines HOW to encrypt (keys, SPI, algorithms)
Lookup Keys	Src IP/Subnet, Dst IP/Subnet, Protocol, Port	Destination IP, Protocol (ESP=50), SPI (32-bit hex)
CLI Command	`ip xfrm policy add ...`	`ip xfrm state add ...`

MACsec (802.1AE), IPsec & Hardware Layer Encryption Studio

MACsec Interface Configuration

SecTAG Frame Breakdown & Encapsulation Overhead

IPsec Encapsulation Parameters

Packet Layer Dissector & Wire Layout

Linux Kernel XFRM Architecture (SAD vs SPD)

Production Hardware & Kernel Blueprints

🔍 Companion Workbenches & Verification Tools

Functional Encryption & Inner-Product Predicates Studio

Threshold ECDSA CGGMP21 & DKLs23 Studio | Multi-Party Institutional Custody

Memory Safety: CHERI Hardware Capabilities & Pointer Provenance Studio

Password Strength & Crack Time Estimator

Why Smart Users Are Switching to This Free Toolkit

The Browser Feature Most People Never Use

Stop Paying for Software You Can Get Free

File Conversion Tricks That Save Hours Every Week

This Free Tool Replaced 5 Paid Apps for Our Team

What Your Browser Can Do Without Any Extensions