<?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[Route Traffic through two IPSEC tunnels (NAT)]]></title><description><![CDATA[<p dir="auto">I'm trying to route traffic from site A to B to C/D/E/F...</p>
<p dir="auto">Site A and B have pfSenses running. Sites C/D/E/F have different firewalls in use.<br />
Between site A and B I have a IPSEC tunnel.<br />
Site B to C/D/E/F are existing IPSEC tunnels that only allow subnets of site B to connect and cannot be changed. The subnet of site A is not allowed to connect directly to C/D/E/F. That's why I'm looking, how I could route the traffic from site A heading towards C/D/E/F and back.</p>
<p dir="auto">I also tried to NAT the traffic from site A on the pfSense to a small IP range of subnet B to get it accepted in the second tunnel to C/D/E/F. That seemed somehow to work, but the traffic didn't find it's way back through the tunnel B to A.</p>
<p dir="auto">Does anybody know, how to configure it on the two pfSense?</p>
<p dir="auto">Cheers<br />
Chris</p>
]]></description><link>https://forum.netgate.com/topic/144678/route-traffic-through-two-ipsec-tunnels-nat</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 13:35:41 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/144678.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Jul 2019 15:24:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Route Traffic through two IPSEC tunnels (NAT) on Wed, 17 Jul 2019 18:15:52 GMT]]></title><description><![CDATA[<p dir="auto">Just define a phase 2 for each of your C/D/E/F networks on the A-B tunnel (the networks are local networks for B and remote for A).</p>
]]></description><link>https://forum.netgate.com/post/853778</link><guid isPermaLink="true">https://forum.netgate.com/post/853778</guid><dc:creator><![CDATA[Morlock]]></dc:creator><pubDate>Wed, 17 Jul 2019 18:15:52 GMT</pubDate></item></channel></rss>