<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>iptables on Deployment</title><link>https://deployment.properties/tags/iptables/</link><description>Recent content in iptables on Deployment</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://deployment.properties/tags/iptables/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Networking Refresh: Network Namespaces</title><link>https://deployment.properties/posts/networking/linux-netns-refresh/</link><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><guid>https://deployment.properties/posts/networking/linux-netns-refresh/</guid><description>&lt;p>In this tutorial we are going to do a refresh on Linux network namespaces. We will start with two namespaces that can&amp;rsquo;t even ping themselves, connect them with a virtual cable, replace that cable with a bridge, give the host a leg on that bridge, and then work our way outward — routing, forwarding, NAT, route specificity, and finally port forwarding back in. Everything is done by hand with &lt;code>ip&lt;/code> and &lt;code>iptables&lt;/code>, so that nothing is hidden behind tooling.&lt;/p>
&lt;p>To simulate an environment we will use a Linux machine via &lt;a href="https://lima-vm.io/">Lima&lt;/a> and the &lt;code>limactl&lt;/code> CLI. Namespaces don&amp;rsquo;t need a complicated topology — one VM is enough, because the whole point is that we&amp;rsquo;re going to build a little network &lt;em>inside&lt;/em> it.&lt;/p></description></item></channel></rss>