<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NAT on No Subject - nosubject.io -</title><link>https://nosubject.io/en/tags/nat/</link><description>Recent content in NAT on No Subject - nosubject.io -</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0900</lastBuildDate><atom:link href="https://nosubject.io/en/tags/nat/index.xml" rel="self" type="application/rss+xml"/><item><title>Deco X20: Port Forwarding Fails</title><link>https://nosubject.io/en/deco-x20-openvpn-port-forwarding-troubleshooting/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0900</pubDate><guid>https://nosubject.io/en/deco-x20-openvpn-port-forwarding-troubleshooting/</guid><description>&lt;p&gt;When setting up port forwarding on Deco X20 (TP-Link), we summarize a case where the destination IP changed unexpectedly after saving, causing traffic to miss the target.&lt;br&gt;
This is handled as an environment-dependent incident and not claimed as a confirmed general defect of all X20 units.&lt;/p&gt;
&lt;h2 id="reference-case"&gt;Reference Case&lt;/h2&gt;
&lt;p&gt;In the TP-Link community, a closely related known case was reported for Deco X20 + Firmware 1.6.1.&lt;br&gt;
In that case (&lt;code&gt;Deco X20 V1 / Firmware 1.6.1&lt;/code&gt;), a port forwarding destination such as &lt;code&gt;192.168.1.x&lt;/code&gt; was rewritten to &lt;code&gt;192.168.0.x&lt;/code&gt;, and changing the subnet mask to &lt;code&gt;255.255.255.0 (/24)&lt;/code&gt; was reported to keep the expected subnet handling.&lt;/p&gt;</description></item></channel></rss>