<?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 axiom0x0</title><link>https://axiom0x0.sh/tags/networking/</link><description>Recent content in Networking on axiom0x0</description><generator>Hugo</generator><language>en-us</language><copyright>© axiom0x0</copyright><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://axiom0x0.sh/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>NetCleaver</title><link>https://axiom0x0.sh/posts/netcleaver/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://axiom0x0.sh/posts/netcleaver/</guid><description>&lt;p&gt;If you do a lot of network recon or incident response, you might end up having to do quite a bit of subnet math. Things like range conversions, CIDR breakdowns, figuring out if two ACLs overlap, carving exclusions out of large blocks. It&amp;rsquo;s a regular thing.&lt;/p&gt;
&lt;p&gt;For a long time, my workflow was what I think everyone does, but won&amp;rsquo;t admit to doing; that is, visit some random online subnet calculator, paste in the CIDR, copy the output, and then close the tab while looking furtively around to see if anyone saw you. Of course, &lt;code&gt;ipcalc&lt;/code&gt; works too, but it only does single network lookups. It also can&amp;rsquo;t compare ranges, batch a file, or tell you if any of the networks you&amp;rsquo;re working overlap.&lt;/p&gt;</description></item></channel></rss>