<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Link-Aggregation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/link-aggregation/</link>
    <description>Recent content in Link-Aggregation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/link-aggregation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted LACP Link Aggregation: systemd networkd vs NetworkManager vs iproute2 (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-19-self-hosted-lacp-link-aggregation-systemd-networkmanager-iproute2-guide/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-19-self-hosted-lacp-link-aggregation-systemd-networkmanager-iproute2-guide/</guid>
      <description>&lt;p&gt;Link Aggregation Control Protocol (LACP), defined in IEEE 802.3ad (now 802.1AX), combines multiple physical network interfaces into a single logical bond for increased bandwidth and redundancy. Self-hosting LACP configuration gives you control over link aggregation without relying on managed switch auto-configuration or proprietary vendor tools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
