<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on wgz.sh</title>
    <link>https://blog.wgz.sh/tags/docker/</link>
    <description>Recent content in Docker on wgz.sh</description>
    <generator>Hugo -- 0.153.1</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 26 Mar 2025 22:24:05 -0400</lastBuildDate>
    <atom:link href="https://blog.wgz.sh/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My NAT Setup for DN42</title>
      <link>https://blog.wgz.sh/posts/nat/</link>
      <pubDate>Wed, 26 Mar 2025 22:24:05 -0400</pubDate>
      <guid>https://blog.wgz.sh/posts/nat/</guid>
      <description>&lt;p&gt;Hey folks,&lt;/p&gt;
&lt;p&gt;Quick tip for anybody using DN42. If you&amp;rsquo;re having an issue making your services reachable on the network you can copy something similar to what I&amp;rsquo;m doing.&lt;/p&gt;
&lt;p&gt;In my lab, I’m running plain Docker, with a container that has a private IP of &lt;code&gt;192.168.77.2&lt;/code&gt;. To make it reachable from a remote peer over WireGuard, I’m using two NAT rules: one for &lt;code&gt;SNAT&lt;/code&gt; and one for &lt;code&gt;DNAT&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Why? Because in the DN42 overlay network, only IPs in the &lt;code&gt;172.20.0.0/14&lt;/code&gt; range are routable. My little slice is &lt;code&gt;172.22.147.160/27&lt;/code&gt;. The whole setup is similar to your home internet with RFC1918 addresses meaning you need to heavily rely on NAT.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
