<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multipath on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/multipath/</link>
    <description>Recent content in Multipath on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/multipath/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted MPTCP Solutions: OpenMPTCProuter vs mptcpd vs Kernel MPTCP</title>
      <link>https://www.pistack.xyz/posts/2026-05-13-self-hosted-mptcp-solutions-openmptcprouter-mptcpd-kernel-guide/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-13-self-hosted-mptcp-solutions-openmptcprouter-mptcpd-kernel-guide/</guid>
      <description>&lt;p&gt;Multipath TCP (MPTCP) allows a single TCP connection to use multiple network paths simultaneously. This means a device can aggregate a wired Ethernet connection, a Wi-Fi link, and a cellular connection into one high-throughput, resilient connection. If one path fails, the connection survives on the remaining paths.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
