<?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[Access to the client terminal connected to the VPN]]></title><description><![CDATA[<p dir="auto">I'm new to the area, starting to study pfSense.<br />
I configured the OpenVPN server on pfSense with Remote Access (SSL/TLS + User Auth), exported the client, the client can connect normally to the company's internal network, accesses the share, everything is correct.<br />
My question is, from the company's network can I connect to this client, access the data from his machine? Make a reverse connection (site-to-client).<br />
This client has network software, which I need to access the software to generate a report.<br />
Or is it only possible to make this connection with the configuration (site-to-site)?<br />
This customer is a partner who only has one machine. It is currently not possible to place another pfSense server on site.</p>
]]></description><link>https://forum.netgate.com/topic/176243/access-to-the-client-terminal-connected-to-the-vpn</link><generator>RSS for Node</generator><lastBuildDate>Wed, 14 Oct 2026 04:40:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/176243.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Dec 2022 01:00:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Access to the client terminal connected to the VPN on Sat, 03 Dec 2022 09:23:14 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/warningsystem">@<bdi>warningsystem</bdi></a> said in <a href="/post/1073478">Access to the client terminal connected to the VPN</a>:</p>
<blockquote>
<p dir="auto">My question is, from the company's network can I connect to this client, access the data from his machine?</p>
</blockquote>
<p dir="auto">The needed data are on the client machine itself, as I understand? Accessing the network behind the client was more complicated and would need a client specific override, when running an access server.</p>
<p dir="auto">You can access the client itself simply by its virtual IP. You can add a SCO anyway to assign a static virtual IP to him.<br />
But you have to allow the access on the clients firewall at all.</p>
<p dir="auto">A trick I'm using for Windows clients to enable access to them is pushing the default route to them, but with a high metric by adding this into the servers custom options box:</p>
<pre><code>push "route-metric 512";push "route 0.0.0.0 0.0.0.0"
</code></pre>
<p dir="auto">This makes the client "smooth", but networking has to be enabled on the client anyway.<br />
However, consider that the pushed metric is applied to any route which is pushed to the client, but worked well.</p>
]]></description><link>https://forum.netgate.com/post/1073500</link><guid isPermaLink="true">https://forum.netgate.com/post/1073500</guid><dc:creator><![CDATA[viragomann]]></dc:creator><pubDate>Sat, 03 Dec 2022 09:23:14 GMT</pubDate></item></channel></rss>