<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Packet Capture on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/packet-capture/</link><description>Recent content in Packet Capture on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Nov 2026 16:23:21 +0100</lastBuildDate><atom:link href="https://networknet.nl/tags/packet-capture/index.xml" rel="self" type="application/rss+xml"/><item><title>Check TCP/443 reachability with netcat</title><link>https://networknet.nl/snippets/netcat-tcp-connectivity/</link><pubDate>Wed, 04 Nov 2026 15:00:00 +0100</pubDate><guid>https://networknet.nl/snippets/netcat-tcp-connectivity/</guid><description>&lt;p>When I troubleshoot routing or firewall access, I start with a quick TCP check from the &lt;strong>Linux VM or Kubernetes pod&lt;/strong> that needs connectivity:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-sh" data-lang="sh">&lt;span class="line">&lt;span class="cl">nc -zv ifconfig.io &lt;span class="m">443&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>In my example, netcat reported &lt;code>succeeded!&lt;/code> for TCP/443. That confirms a TCP connection to the resolved address for &lt;code>ifconfig.io&lt;/code> from the tested client at that moment. It does &lt;strong>not&lt;/strong> prove which route was taken, which firewall or ZTNA rule matched, or whether HTTPS/TLS works.&lt;/p></description></item></channel></rss>