<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Layer2 on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/layer2/</link><description>Recent content in Layer2 on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/layer2/index.xml" rel="self" type="application/rss+xml"/><item><title>MACsec (IEEE 802.1AE)</title><link>https://lesitedefrancois.be/en/security/macsec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/macsec/</guid><description>&lt;p&gt;&lt;strong&gt;MACsec (MAC Security, IEEE 802.1AE)&lt;/strong&gt; is an IEEE standard, first published in 2006 and supported in the Linux kernel since 4.6 (2016), that encrypts and authenticates Ethernet frames at layer 2 — hop by hop between directly connected devices. Its operating layer is what distinguishes it from &lt;strong&gt;IPsec&lt;/strong&gt; (layer 3) and &lt;strong&gt;TLS&lt;/strong&gt; (layer 4): MACsec wraps Ethernet frames, not IP packets or TCP streams, so it can protect every byte that traverses a link segment regardless of what protocol it carries. ARP replies, DHCP offers, LLDP frames, routing protocol adjacencies, and layer-2 broadcast traffic are all encrypted and authenticated alongside application data — something neither IPsec nor TLS can accomplish because both require an IP header to already be present and unenforced. The topology implication of this is that MACsec is &lt;strong&gt;link-local and hop-by-hop&lt;/strong&gt;: it encrypts between two directly adjacent Ethernet peers (a host and a switch, or two switches), decrypts at each hop for forwarding decisions, and re-encrypts toward the next hop. It cannot stretch across a routed boundary; for that, IPsec is the right tool.&lt;/p&gt;</description></item></channel></rss>