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
I moved all VPN type functions to SSH. One port, no management. Clients can be pre-configured to tunnel the needed ports, so no configuration by the client needed. Very secure. All the applications we needed (file transfer, email, intranet web access, remote GUI application execution, etc.) can be transferred over SSH tunnels. Wide availability of clients (even Java implementations, loadable via web browser). Available for every platform and architecture, and cross-platform compatible. As an ad-hoc solution, no resources are consumed when the connection is not in use. Works easily with NAT (port forward) and firewalls. Support one client or 10,000 makes no different (size the server for concurrent use).