<?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[IPSec tunnel with NAT]]></title><description><![CDATA[<p dir="auto">Hello all,</p>
<p dir="auto">I have a customer request for the below scenario ,</p>
<p dir="auto">Site1 - PFsense with 3 NIC<br />
LAN,WAN and MGMT<br />
LAN subnet : 10.101.60.0/24</p>
<p dir="auto">Site2 - Cisco ASA<br />
LAN subnet : 10.23.88.0/22</p>
<p dir="auto">So the request comes from the network engineer in site2 . Because he uses somethere the lan 10.101.60.0/24 he give me a private IP to enter it in pfsense and use this IP as an interesting traffic and NAT ports from this IP to LAN subner behind pfsense. So in pfsense in remote network i have his network 10.23.88.0/22 and in site 2 in remote network he enters as a remote nework the /32 ip he gave me to add to pfsense .</p>
<p dir="auto">My question is if i must do something in the nat/binat section in phase 2. If i just enter as a virtual ip the /32 ip and then create NAT rules is this going to work ?</p>
<p dir="auto">Thanks a lot</p>
]]></description><link>https://forum.netgate.com/topic/113401/ipsec-tunnel-with-nat</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 16:43:36 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/113401.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 22 Mar 2017 14:42:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to IPSec tunnel with NAT on Fri, 24 Mar 2017 12:11:46 GMT]]></title><description><![CDATA[<p dir="auto">Any ideas guys ? A reminder for the above post , We want traffic from site1 to site2 to appear from a single /32 IP .</p>
<p dir="auto">Thanks a lot</p>
]]></description><link>https://forum.netgate.com/post/688899</link><guid isPermaLink="true">https://forum.netgate.com/post/688899</guid><dc:creator><![CDATA[merlinios]]></dc:creator><pubDate>Fri, 24 Mar 2017 12:11:46 GMT</pubDate></item></channel></rss>