<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Debugging - Tag - vo.rs</title><link>https://vo.rs/tags/debugging/</link><description>Debugging - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 17 Jul 2025 16:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/debugging/" rel="self" type="application/rss+xml"/><item><title>Container Networking Debugging: tcpdump, nsenter, and What Packets Are Actually Doing</title><link>https://vo.rs/story/container-networking-debugging-tcpdump-nsenter-and-what-packets-are-actually-doing/</link><description>&lt;p&gt;Container networking is one of those things that works beautifully right up until it doesn&amp;rsquo;t, at which point you&amp;rsquo;re staring at &lt;code&gt;connection refused&lt;/code&gt; while three different layers of NAT, bridge interfaces and iptables rules all insist they&amp;rsquo;re innocent. The frustrating part is that the container is usually a minimal image with no &lt;code&gt;ping&lt;/code&gt;, no &lt;code&gt;curl&lt;/code&gt;, no &lt;code&gt;tcpdump&lt;/code&gt; — nothing you&amp;rsquo;d use to actually see what&amp;rsquo;s happening. So you guess, you restart things, and eventually it &amp;ldquo;fixes itself,&amp;rdquo; which is the worst possible outcome because now you don&amp;rsquo;t know what was wrong. Here&amp;rsquo;s how to stop guessing.&lt;/p&gt;</description><pubDate>Thu, 17 Jul 2025 16:00:00 +0000</pubDate></item></channel></rss>