<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[internal external nat problem]]></title><description><![CDATA[<p dir="auto">Hello,<br />
how I can make the external nat policy work from internal network ?<br />
thanks</p>
]]></description><link>https://forum.netgate.com/topic/142394/internal-external-nat-problem</link><generator>RSS for Node</generator><lastBuildDate>Wed, 14 Oct 2026 14:00:24 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/142394.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 09 Apr 2019 14:48:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to internal external nat problem on Tue, 09 Apr 2019 14:49:46 GMT]]></title><description><![CDATA[<p dir="auto">https://doc.pfsense.org/index.php/Why_can't_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks</p>
<p dir="auto">Use split DNS.</p>
]]></description><link>https://forum.netgate.com/post/836050</link><guid isPermaLink="true">https://forum.netgate.com/post/836050</guid><dc:creator><![CDATA[KOM]]></dc:creator><pubDate>Tue, 09 Apr 2019 14:49:46 GMT</pubDate></item></channel></rss>