<?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[OpenVPN 2.0-Beta Client to 1.2.3 Server &quot;won&#x27;t route&quot; or firewalled?]]></title><description><![CDATA[<p dir="auto">This could easily be a PEBKAC- I have limited-enough experience with OpenVPN that I may have just configured something wrong, but as-yet I've been unable to get my OpenVPN Site-to-Site to "work" properly.</p>
<p dir="auto">"Remote" pfSense - 192.168.4.1/24 - 2.0, snapshot from 2010-02-15 around 8 PM EST? (client)<br />
"Central" pfSense - 172.16.0.254/24 (CARP to 172.16.0.1) - 1.2.3-RELEASE (server)</p>
<p dir="auto">Using 'shared key' with OpenVPN, and the tunnel is configured as 172.16.254.0/24<br />
(172.16.254.1 being OpenVPN server, .2 being the client, I believe?)</p>
<p dir="auto">"Remote" has a PASS ALL * * * * rule in the OpenVPN configuration.</p>
<p dir="auto">Both pfSense boxes are able to ping and communicate with the machines on the other end of the tunnel's subnet.</p>
<p dir="auto">The workstations on both ends of the tunnel are able to ping both sides of the "Tunnel"'IPs - 172.16.254.1 and 172.16.254.2</p>
<p dir="auto">However, no workstations/whatever on either end of the tunnel are able to ping or otherwise reach the machines on the opposite end.</p>
<p dir="auto">Worth noting - the 1.2.3 machine <em>may</em> have had firewall rules enter into a temporarily-defined "OPT" interface associated with "TUN" - and may not have been rebooted since.  (That is likely my nest section to check out)</p>
]]></description><link>https://forum.netgate.com/topic/21546/openvpn-2-0-beta-client-to-1-2-3-server-won-t-route-or-firewalled</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 16:55:14 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/21546.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 17 Feb 2010 01:00:39 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to OpenVPN 2.0-Beta Client to 1.2.3 Server &quot;won&#x27;t route&quot; or firewalled? on Wed, 17 Feb 2010 18:12:10 GMT]]></title><description><![CDATA[<p dir="auto">Looks like the 1.2.3 machine needed to be rebooted - appears that there's a bug (or at least unexpected behavior) regarding OpenVPN-interface assignment and filtering.  After the reboot of the 1.2.3 machine, everything works more or less as expected.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/overand">@<bdi>overand</bdi></a>:</p>
<blockquote>
<p dir="auto">Worth noting - the 1.2.3 machine <em>may</em> have had firewall rules enter into a temporarily-defined "OPT" interface associated with "TUN" - and may not have been rebooted since.  (That is likely my nest section to check out)</p>
</blockquote>
]]></description><link>https://forum.netgate.com/post/223403</link><guid isPermaLink="true">https://forum.netgate.com/post/223403</guid><dc:creator><![CDATA[overand]]></dc:creator><pubDate>Wed, 17 Feb 2010 18:12:10 GMT</pubDate></item></channel></rss>