<?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[Tunnel From Vultr PFSense to Physical PFSense]]></title><description><![CDATA[<p dir="auto">First post btw.</p>
<p dir="auto">Bottom Line: I created an IPSec tunnel that establishes and stays up. I can ping from my homelab to Vultr network through the tunnel using private addresses. I cannot ping homelab from Vultr though, this is really frustrating. I have been working on this for two days. I am fairly new to this, so hopefully I have made a simple mistake.</p>
<p dir="auto">Scenario:</p>
<p dir="auto">Homelab - 10.10.x.x/24 Network. 1 Physical nano server with PFSense installed and a Windows 10 Pro box This network can ping Vultr clients, no problem.</p>
<p dir="auto">Vultr - 192.168.x.x/24 Network. 1 PFSense instance and 1 Windows 2016 Server. These instances can ping each other but not Homelab clients.</p>
<p dir="auto">I can provide more info as we go. Thanks in advance.</p>
]]></description><link>https://forum.netgate.com/topic/155356/tunnel-from-vultr-pfsense-to-physical-pfsense</link><generator>RSS for Node</generator><lastBuildDate>Sat, 12 Sep 2026 14:39:35 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/155356.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 17 Jul 2020 17:22:57 GMT</pubDate><ttl>60</ttl></channel></rss>