<?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[On IPsec and NAT again - SOLVED]]></title><description><![CDATA[<p dir="auto">I have a site to site IPsec tunnel:</p>
<p dir="auto">| Remote LAN  | Remote Gateway  |          | pfSense Gateway |    Local LAN   |<br />
| 10.1.0.0/16 |   Remote  IP    | &lt;&lt;=== &gt;&gt; |    pfSense IP   | 192.168.1.0/24 |</p>
<p dir="auto">The IPsec phase 1/2 goes well, the connection is established and the traffic flows between pfSense Gateway and Remote LAN clients (thanks to this: <a href="http://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN%3F" target="_blank" rel="noopener noreferrer nofollow ugc">http://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN%3F</a>)</p>
<p dir="auto">Now I have the following problem: the local subnet address that I have to use in phase 2 isn't my real 192.168.1.0/24 but another one (for eg. 192.168.2.0/24 because it is imposed by remote restrictions that I can't change), so I have to translate addresses in some way.<br />
I don't know whether this is possible or not, after reading some posts I suspect it isn't, but perhaps I'm wrong.<br />
I tried several ways: virtual IP on LAN, firewall/NAT rules, outbound NAT rules, source NAT, but without luck :(</p>
<p dir="auto">Some guy has an idea on how to accomplish this task? Or, is it really not possible due to pf limitations?<br />
Do I have to change my local LAN addresses? (this will be very expensive!)</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/51597/on-ipsec-and-nat-again-solved</link><generator>RSS for Node</generator><lastBuildDate>Sun, 15 Mar 2026 05:50:39 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/51597.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Jan 2013 16:03:36 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to On IPsec and NAT again - SOLVED on Fri, 04 Jan 2013 09:35:48 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for the explanation.<br />
For those who have the same problem, I've solved it with a workaround, for now.<br />
I've:</p>
<ul>
<li>
<p dir="auto">assigned a virtual IP (192.168.2.1) on LAN interface</p>
</li>
<li>
<p dir="auto">set up apposite rules on firewall/NAT section (included Manual Outbound NAT)</p>
</li>
<li>
<p dir="auto">added a new address (for eg. 192.168.2.5) on the network card of internal Windows machine and a new gateway 192.168.2.1 (with a higher metric than default to not interfere with the previous state)</p>
</li>
<li>
<p dir="auto">in the Windows machine set up a new permanent route to 10.1.0.0/16 net via 192.168.2.1 gateway</p>
</li>
</ul>
<p dir="auto">It works!</p>
]]></description><link>https://forum.netgate.com/post/370819</link><guid isPermaLink="true">https://forum.netgate.com/post/370819</guid><dc:creator><![CDATA[SuperC]]></dc:creator><pubDate>Fri, 04 Jan 2013 09:35:48 GMT</pubDate></item><item><title><![CDATA[Reply to On IPsec and NAT again - SOLVED on Fri, 04 Jan 2013 06:20:40 GMT]]></title><description><![CDATA[<p dir="auto">Possible in 2.1, not in any earlier versions. Usual work around is to do NAT on one box, IPsec on another. Pre-2.1, they can't both be on the same system, IPsec happens before NAT can happen.</p>
]]></description><link>https://forum.netgate.com/post/370805</link><guid isPermaLink="true">https://forum.netgate.com/post/370805</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Fri, 04 Jan 2013 06:20:40 GMT</pubDate></item></channel></rss>