<?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[NAT Problems - 2.0 RC1 April 5 build]]></title><description><![CDATA[<p dir="auto">I have a 1:1 NAT set up on a WAN address.  My problem is that when the packet traverses the pfsense box, it is keeping the original source IP address and I need it to be natted to the pfsense LAN interface IP so that the internal server knows how to route it back out.  The pfsense is not the default gateway for the LAN.<br />
A sniff at the server shows the packets arriving with the original client IP instead of the pfsense IP.  Any ideas would be welcome.<br />
<img src="/public/_imported_attachments_/1/NAT.png" alt="NAT.png" class=" img-fluid img-markdown" /><br />
<img src="/public/_imported_attachments_/1/NAT.png_thumb" alt="NAT.png_thumb" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/32467/nat-problems-2-0-rc1-april-5-build</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 05:52:58 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/32467.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 06 Apr 2011 19:06:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NAT Problems - 2.0 RC1 April 5 build on Mon, 11 Apr 2011 14:56:35 GMT]]></title><description><![CDATA[<p dir="auto">1:1 NAT on WAN wouldn't help for that.</p>
<p dir="auto">You need to be on manual outbound NAT, and have an outbound NAT rule (or maybe 1:1) on <strong>LAN</strong> in order to translate in the way you want.</p>
]]></description><link>https://forum.netgate.com/post/274521</link><guid isPermaLink="true">https://forum.netgate.com/post/274521</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Mon, 11 Apr 2011 14:56:35 GMT</pubDate></item></channel></rss>