<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ubuntu Networking on MeerStory</title><link>https://linux.meerstory.com/categories/ubuntu-networking/</link><description>Recent content in Ubuntu Networking on MeerStory</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Oct 2026 01:57:42 +0900</lastBuildDate><atom:link href="https://linux.meerstory.com/categories/ubuntu-networking/index.xml" rel="self" type="application/rss+xml"/><item><title>The Complete Guide to Inspecting Network Ports with Linux ss</title><link>https://linux.meerstory.com/ubuntu/20261009_015658_18/</link><pubDate>Fri, 09 Oct 2026 01:57:42 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261009_015658_18/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Diagnosing socket states and tracing open communication channels sits at the core of effective Linux system troubleshooting. While legacy toolsets like &lt;code>netstat&lt;/code> were once ubiquitous, the modern Linux ecosystem relies on the significantly faster and more capable &lt;code>ss&lt;/code> utility. In this hands-on walkthrough, we dive into leveraging &lt;code>ss&lt;/code> to inspect active connections, monitor listening services, identify bind ports, and correlate network sockets with their controlling process IDs.&lt;/p>
&lt;h2 id="1-preparing-the-environment-and-inspecting-global-socket-statistics">1. Preparing the Environment and Inspecting Global Socket Statistics&lt;/h2>
&lt;p>The &lt;code>ss&lt;/code> command-line utility ships out of the box with the &lt;code>iproute2&lt;/code> package on modern Ubuntu distributions. Begin by updating the local package index and ensuring &lt;code>iproute2&lt;/code> is fully installed and up to date.&lt;/p></description></item></channel></rss>