<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networking on Nalar</title>
    <link>https://nalar.dev/tags/networking/</link>
    <description>Recent content in Networking on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Network Troubleshooting with ip, ss, dig, and curl</title>
      <link>https://nalar.dev/linux-network-troubleshooting-ip-ss-dig-curl/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/linux-network-troubleshooting-ip-ss-dig-curl/</guid>
      <description>&lt;p&gt;When a Linux service is &amp;ldquo;unreachable,&amp;rdquo; the failure can be in several different layers: the local interface, routing, a listening socket, DNS, a firewall, TLS, or the application itself.&lt;/p&gt;&#xA;&lt;p&gt;Randomly restarting services makes diagnosis harder. A better approach is to move from local state outward and identify the first layer that does not behave as expected.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-confirm-the-interface-and-address&#34;&gt;1. Confirm the interface and address&lt;/h2&gt;&#xA;&lt;p&gt;Start with the addresses configured on the host:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
