Linked by David Bogen on Mon 26th Jan 2004 04:47 UTC
For many systems administrators, choosing and managing a VPN system is often quite a headache. Inflexible clients, servers, and protocols often prevent VPN's from being smoothly integrated into an already functioning network. The fact that many VPN clients are installed on users' home computers, well out of the reach of the systems administration team, often means that troubleshooting and upgrading VPN systems is time consuming and a struggle for both admins and users.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
>"The port no is predefined per tunnel. So 5001 is set on >the server and the client for that tunnel."
>Do you have to do this manually? If you do this seems >like it would be a nightmare to administer more than a >few clients.
>Also I was wondering about the speed of SSL encryption >vs. hardware based IPSEC.
Yes it's manual but it takes 2 mins to create a tunnel. I've written my own scripts which cuts it down to a few seconds, but once you have good configs then you can use them as templates for the other tunnels. One template per os is fine.
The first patches are coming thru for multiple tunnels to a single port but dont expect anything in the mainline too soon.
I dont know anything about hardware acceleration but there's quite a few comments on the openvpn mailing list.