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 article says that I have to open a firewall port for >every user. In an Enterprise environment, this is simply >unacceptable. I can't go opening 500 or 1,000 ports for >VPN users. Other VPN solutions run over ONE port. The >firewall port issue alone is enough to discount OpenVPN >as a solution. Is the port information correct, or am I >misunderstanding?
It's messy yes, but not unacceptable. good scripting can manage the ports. It's no more insecure, the last 999 ports have the same security as the 1st 1.
If you are in an Enterprise environment then chances are this will not be your solution because it is not backed by a bluechip support company. If this is not a problem then you could write a decent management script(s) in a day. One day is nothing for 500-1000 tunnels.