<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conntrack on Marcello Barnaba</title>
    <link>https://sindro.me/it/tags/conntrack/</link>
    <description>Recent content in Conntrack on Marcello Barnaba</description>
    <generator>Hugo</generator>
    <language>it</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sindro.me/it/tags/conntrack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Failover mwan3 senza connessioni appese</title>
      <link>https://sindro.me/it/posts/2026-05-01-mwan3-failover-conntrack/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sindro.me/it/posts/2026-05-01-mwan3-failover-conntrack/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; &lt;a href=&#34;https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3&#34; target=&#34;_blank&#34;&gt;mwan3&lt;/a&gt;&#xA;sposta i flussi &lt;em&gt;nuovi&lt;/em&gt; quando un uplink cade. I flussi esistenti&#xA;restano inchiodati al percorso morto: il conntrack se li ricorda,&#xA;il flow offload del firewall continua a spedire pacchetti lungo&#xA;quel percorso, e i socket TCP a vita lunga restano appesi finché&#xA;l&amp;rsquo;applicazione non se ne accorge e si riconnette. L&amp;rsquo;opzione nativa&#xA;&lt;code&gt;flush_conntrack&lt;/code&gt; è un&amp;rsquo;atomica globale. La soluzione è un&#xA;&lt;code&gt;/etc/mwan3.user&lt;/code&gt; da quindici righe che fa un flush &lt;em&gt;selettivo&lt;/em&gt; del&#xA;conntrack per mark mwan3, solo sull&amp;rsquo;evento &lt;code&gt;disconnected&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
