SSL VPN

Sat Jun 15 11:49:29 UTC 2019

The former.

Mark.

On 13/Jun/19 20:25, Jasper Backer wrote:
>
> Just wondering, is the client export actually tied to the logged in
> user, or can every user download all other VPN profiles (which
> hopefully are of little use as credentials are likely unknown)? It
> used to be that way, would be nice if it is tied to just the logged in
> user.
>
> Cheers,
>
> Jasper
>
> On 13-06-19 20:06, Matt Harris wrote:
>> On Thu, Jun 13, 2019 at 12:59 PM Mark Tinka <mark.tinka at seacom.mu
>> <mailto:mark.tinka at seacom.mu>> wrote:
>>
>>
>>     OpenVPN in pfSense?
>>
>>     We run tons of these around the world.
>>
>>     Mark.
>>
>>
>> With the client config generator package, "openvpn-client-export",
>> installed, this is imho the best option for an end-user VPN. pfSense
>> has a much nicer UI than OpenVPN AS, and that UI also supports other
>> things you might need (like routing protocols via bird or quagga,
>> managing the firewall, etc) as well. I can't see any reason to pay
>> money for OpenVPN AS when you compare it to what you get for free
>> with pfSense.  The NetGate pfSense appliances are quite nicely
>> spec'd, too, if you just have cash burning a hole in your pocket.  It
>> also easily ties in OpenVPN authentication to RADIUS or LDAP, and
>> getting it working with Active Directory on the backend is trivially
>> simple. 
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190615/4da4c2e2/attachment.html>