<?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[Port Forward from OpenVPN to IPSEC]]></title><description><![CDATA[<p dir="auto">Hi everyone,<br />
Here's the situation: I'm managing a pfSense instance configured with three interfaces - WAN, LAN (192.168.190.0/24), and an OpenVPN setup for roadwarrior clients (172.16.0.0/24 subnet) with routing to the LAN.</p>
<p dir="auto">I need enabling these OpenVPN clients to connect to a couple of hosts on a remote subnet (10.0.0.0/24), which is connected via IPSec Site-to-Site (S2S) between my pfSense and a firewall (let's call it FW02) owned by another company. Both 172.16.0.0/24 (OVPN) and 10.0.0.0/24 (IPSEC) are connected to the LAN interface (192.168.190.0/24) . There is no direct routing between OVPN and IPSEC. I thought I could link some hosts beetween the two with a Port Forward on the LAN, but so far my configurations have been unsuccessful.<br />
Is a NAT/Port Forward feasible or do I absolutely need to route OVPN subnet through the IPSEC?</p>
<p dir="auto">Can you please point me in the right direction?<br />
The scheme would be:<br />
OVPN -&gt; LAN -&gt; NAT/PAT -&gt; IPSEC</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/183163/port-forward-from-openvpn-to-ipsec</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 03:51:43 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/183163.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Oct 2023 12:47:31 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Port Forward from OpenVPN to IPSEC on Mon, 02 Oct 2023 19:48:50 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/viragomann">@<bdi>viragomann</bdi></a> That Worked!</p>
<p dir="auto">Thanks a lot <img src="https://forum.netgate.com/assets/plugins/nodebb-plugin-emoji/emoji/android/270c.png?v=717669fab53" class="not-responsive emoji emoji-android emoji--v" style="height:23px;width:auto;vertical-align:middle" title=":v:" alt="✌" /></p>
]]></description><link>https://forum.netgate.com/post/1128177</link><guid isPermaLink="true">https://forum.netgate.com/post/1128177</guid><dc:creator><![CDATA[Sysman]]></dc:creator><pubDate>Mon, 02 Oct 2023 19:48:50 GMT</pubDate></item><item><title><![CDATA[Reply to Port Forward from OpenVPN to IPSEC on Mon, 02 Oct 2023 15:06:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sysman">@<bdi>Sysman</bdi></a> said in <a href="/post/1128119">Port Forward from OpenVPN to IPSEC</a>:</p>
<blockquote>
<p dir="auto">I thought I could link some hosts beetween the two with a Port Forward on the LAN</p>
</blockquote>
<p dir="auto">This might work if also do masquerading on them. But this seems to be a dirty workaround.</p>
<blockquote>
<p dir="auto">Is a NAT/Port Forward feasible or do I absolutely need to route OVPN subnet through the IPSEC?</p>
</blockquote>
<p dir="auto">I assume, you have a policy based IPSec. So yes, it could be routed and natted over an additional LAN host, but the clean solution is to add a phase 2 for the OpenVPN tunnel.</p>
<p dir="auto">If you cannot make changes the remote site you can try to nat the traffic in an additional phase 2 to an IP out of the LAN subnet, but this isn't accepted by all IPSec implementations.</p>
]]></description><link>https://forum.netgate.com/post/1128141</link><guid isPermaLink="true">https://forum.netgate.com/post/1128141</guid><dc:creator><![CDATA[viragomann]]></dc:creator><pubDate>Mon, 02 Oct 2023 15:06:25 GMT</pubDate></item></channel></rss>