<?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[1 to 1 NAT through IPsec]]></title><description><![CDATA[<p dir="auto">Hi! I'm trying to make my servers on an internal network exit the firewall through an IPsec tunnel with a public IP.</p>
<p dir="auto">I work at an ISP and have routed a /27 public network through an IPsec into my pfSense firewall at home. I've previously used FortiGate with policy-routing and virtual ips, but it doesn't seem to work the same way with pfSense.</p>
<p dir="auto">On my P2 I've specified the /27 network as local subnet, and 0.0.0.0/0 as remote subnet.</p>
<p dir="auto">In NAT 1:1:<br />
Interface: IPsec<br />
External IP: xxx.xxx.93.13<br />
Internal IP: 172.16.0.65<br />
Destination IP: *</p>
<p dir="auto">I had to port forward ICMP with destination xxx.xxx.93.13 to 172.16.0.65 to make my pings (from AWS) show up in tcpdump.<br />
With NAT-reflection enabled, I can access the server with its public IP locally.</p>
<p dir="auto">Outbound NAT is set to manual, with a mapping that says:<br />
Interface: IPsec<br />
Source: 172.16.0.65<br />
Source port: *<br />
Destination: *<br />
Destination port: *<br />
NAT address: xxx.xxx.93.13<br />
NAT port: *</p>
<p dir="auto">Am I missing something? I've tried everything I could think of, and getting pretty frustrated.</p>
]]></description><link>https://forum.netgate.com/topic/125064/1-to-1-nat-through-ipsec</link><generator>RSS for Node</generator><lastBuildDate>Fri, 06 Mar 2026 18:23:35 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/125064.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 29 Dec 2017 13:50:08 GMT</pubDate><ttl>60</ttl></channel></rss>