<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Nat - vo.rs</title><link>https://vo.rs/tags/nat/</link><description>Latest from the Nat desk at 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>Fri, 01 Mar 2024 15:52:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/nat/" rel="self" type="application/rss+xml"/><item><title>Double-NAT and How to Escape It</title><link>https://vo.rs/story/double-nat-and-how-to-escape-it/</link><description>&lt;p&gt;You forwarded the port. You checked it three times. The service works perfectly from inside the house and is stone dead from the outside, and you&amp;rsquo;re starting to doubt your own competence. Before you rewrite the firewall rule for the fourth time, check one thing: how many times your traffic gets NATed on the way out. Because if the answer is &amp;ldquo;twice&amp;rdquo;, the port forward you configured on your router never had a chance — the packet gets translated again upstream by a device you don&amp;rsquo;t control, and your forward is pointing at the wrong layer of the onion. This is double-NAT, and it&amp;rsquo;s one of the most common reasons a home self-hoster&amp;rsquo;s inbound access mysteriously refuses to work.&lt;/p&gt;</description><pubDate>Fri, 01 Mar 2024 15:52:00 +0000</pubDate></item></channel></rss>