<?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[Can&#x27;t add second IPSec connection with the same remote gateway]]></title><description><![CDATA[<p dir="auto">I have a Public IP Range (for instance: 70.10.10.8/29 and added them as a Virtual IP address to the WAN interface. Then I create the first IPSec connection, it creates successfully.<br />
Phase 1<br />
Interface: 70.10.10.10<br />
Remote Gateway: 80.10.10.10</p>
<p dir="auto">But when I create a second IPSec connection with a different interface but the same Remote Gateway, it gives an error: <strong>"The remote gateway "80.10.10.10" is already used by phase1"</strong>.<br />
Phase 1<br />
Interface: 70.10.10.11<br />
Remote Gateway: 80.10.10.10</p>
<p dir="auto">Why can't I create the second phase 1 with a different interface IP address but the same Remote Gateway?</p>
]]></description><link>https://forum.netgate.com/topic/162486/can-t-add-second-ipsec-connection-with-the-same-remote-gateway</link><generator>RSS for Node</generator><lastBuildDate>Sat, 05 Sep 2026 23:18:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/162486.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 28 Mar 2021 07:21:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can&#x27;t add second IPSec connection with the same remote gateway on Thu, 01 Apr 2021 08:02:50 GMT]]></title><description><![CDATA[<p dir="auto">Thank you for your reply. I upgraded our current pfsense 2.4.5 p1 to 2.5.0, but then ipsec connections don't work and there is nothing in Description tab of Phase 1 any more.</p>
]]></description><link>https://forum.netgate.com/post/975619</link><guid isPermaLink="true">https://forum.netgate.com/post/975619</guid><dc:creator><![CDATA[emammadov]]></dc:creator><pubDate>Thu, 01 Apr 2021 08:02:50 GMT</pubDate></item><item><title><![CDATA[Reply to Can&#x27;t add second IPSec connection with the same remote gateway on Wed, 31 Mar 2021 16:00:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/emammadov">@<bdi>emammadov</bdi></a> see Advanced Options:<br />
<img src="/assets/uploads/files/1617206362657-screenshot-from-2021-03-31-18-56-58.png" alt="Screenshot from 2021-03-31 18-56-58.png" class=" img-fluid img-markdown" /></p>
<p dir="auto"><a href="https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/configure.html#advanced-options" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/configure.html#advanced-options</a></p>
]]></description><link>https://forum.netgate.com/post/975552</link><guid isPermaLink="true">https://forum.netgate.com/post/975552</guid><dc:creator><![CDATA[viktor_g]]></dc:creator><pubDate>Wed, 31 Mar 2021 16:00:23 GMT</pubDate></item><item><title><![CDATA[Reply to Can&#x27;t add second IPSec connection with the same remote gateway on Wed, 31 Mar 2021 15:07:20 GMT]]></title><description><![CDATA[<p dir="auto">Because it creates a conflict. By default the system sets up static routes to the remote gateway over the appropriate WAN, and having a duplicate would break that since you can't have two routes to the same destination.</p>
<p dir="auto">On 2.5.x/21.02.x there is a <strong>Gateway duplicates</strong> option you can enable on both tunnels to allow that configuration to work, but read the text for the option carefully.</p>
]]></description><link>https://forum.netgate.com/post/975530</link><guid isPermaLink="true">https://forum.netgate.com/post/975530</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Wed, 31 Mar 2021 15:07:20 GMT</pubDate></item></channel></rss>