<?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[Using 2nd pfsense box for openvpn behind pfsense gw]]></title><description><![CDATA[<p dir="auto">Currently I have a pfsense 2.0 acting as GW.<br />
To offload this GW, I want to use a second pfsense box behind this one to act as openvpn server.</p>
<p dir="auto">On the GW:</p>
<ul>
<li>wan: public ip + 2nd ip via proxy arp</li>
<li>lan: 192.168.10.254/24 + ip alias for 192.168.100.254/24</li>
</ul>
<p dir="auto">normal lan machines are running in 192.168.10.254</p>
<p dir="auto">Configured second pfsense currently</p>
<ul>
<li>wan: 192.168.100.253/24</li>
<li>lan 192.168.10.153 (so I can access its interface via normal lan)</li>
</ul>
<p dir="auto">2nd public ip is 1:1 natted to the second pfsense box</p>
<p dir="auto">I can connect from outside via ssh on the 2nd public ip and work from there</p>
<p dir="auto">I need the openvpn to function on the second pfsense, reachable via the 2nd public ip.<br />
Currently running vpn on the first gw, and this works ok.<br />
When trying to connect to the open vpn server on the 2nd box, I can see the client and server trying to establish a connection, but failing on timeouts. It seems that traffic of the vpn server does not reach the client.</p>
<p dir="auto">Any help/pointers would be great.</p>
]]></description><link>https://forum.netgate.com/topic/48745/using-2nd-pfsense-box-for-openvpn-behind-pfsense-gw</link><generator>RSS for Node</generator><lastBuildDate>Wed, 11 Mar 2026 04:14:32 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/48745.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Sep 2012 11:41:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Using 2nd pfsense box for openvpn behind pfsense gw on Mon, 01 Oct 2012 17:32:17 GMT]]></title><description><![CDATA[<p dir="auto">Following cmb's remark: we put the vpn on the primary pfsense box (and upgrading its hardware a bit)</p>
]]></description><link>https://forum.netgate.com/post/358335</link><guid isPermaLink="true">https://forum.netgate.com/post/358335</guid><dc:creator><![CDATA[hans-d]]></dc:creator><pubDate>Mon, 01 Oct 2012 17:32:17 GMT</pubDate></item><item><title><![CDATA[Reply to Using 2nd pfsense box for openvpn behind pfsense gw on Sun, 23 Sep 2012 04:18:03 GMT]]></title><description><![CDATA[<p dir="auto">You're creating routing complications doing that. In most all cases there isn't a requirement to offload such functionality and it's best left on your main firewall to avoid the routing complications inherent in the type of setup you're attempting.</p>
<p dir="auto">You can, by adding an appropriate static route on the box that's the default gateway of the network, and checking the option to bypass filtering for static route networks under System&gt;Advanced. It just sounds like you don't really need to do that and are probably best served not doing so.</p>
]]></description><link>https://forum.netgate.com/post/357122</link><guid isPermaLink="true">https://forum.netgate.com/post/357122</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Sun, 23 Sep 2012 04:18:03 GMT</pubDate></item><item><title><![CDATA[Reply to Using 2nd pfsense box for openvpn behind pfsense gw on Thu, 20 Sep 2012 13:37:44 GMT]]></title><description><![CDATA[<p dir="auto">might be an issue with nat &amp; udp ovpn tunnels, have you tried running ovpn on tcp to see if this resolves it ?</p>
<p dir="auto">if not, please supply more info (server configs, traceroutes, packets captures, …)</p>
]]></description><link>https://forum.netgate.com/post/356811</link><guid isPermaLink="true">https://forum.netgate.com/post/356811</guid><dc:creator><![CDATA[heper]]></dc:creator><pubDate>Thu, 20 Sep 2012 13:37:44 GMT</pubDate></item></channel></rss>