<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nftables on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/nftables/</link>
    <description>Recent content in Nftables on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 07 Jun 2026 10:34:30 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/nftables/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting Local Port Conflicts with ss and nftables on a Multi-Service Linux Host</title>
      <link>https://linuxeries.org/post/2026-06-07-troubleshooting-local-port-conflicts-with-ss-/</link>
      <pubDate>Sun, 07 Jun 2026 10:34:30 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-07-troubleshooting-local-port-conflicts-with-ss-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-local-port-conflicts&#34;&gt;Introduction to Local Port Conflicts&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when running a multi-service Linux host - local port conflicts can be a real headache. These conflicts arise when two or more services attempt to bind to the same port, causing one or more of them to fail. To troubleshoot local port conflicts, I usually start with the &lt;code&gt;ss&lt;/code&gt; command and &lt;code&gt;nftables&lt;/code&gt; on a Linux system.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-port-conflicts&#34;&gt;Understanding Port Conflicts&lt;/h2&gt;&#xA;&lt;p&gt;A port conflict occurs when a service tries to bind to a port that is already in use by another service. This can happen when multiple services are configured to use the same port, or when a service is not properly configured to use a unique port. Don&amp;rsquo;t bother with the traditional &lt;code&gt;netstat&lt;/code&gt; command - the &lt;code&gt;ss&lt;/code&gt; command is a more modern replacement.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
