Overhead
VPN tunnels impose overhead for dial-in users: encryption algorithms may impact the performance of the user's system, there will be an increased protocol header overhead, authentication latency will increase, PPP and IP compression will perform poorly (compared to a direct link), and modem compression won't work at all.
Support issues
Replacing direct-dial links with VPN tunnels may produce some very painful faultfinding missions. Due to the complexity of VPN carrier networks, the opportunities for "hand-washing" are enormous.
Reconnection time
Using tunneling may increase the reconnection time for dial users. With the VPN carrier L2TP model, the client has to go through two authentication phases: one on contacting the VPN carrier POP, and another on contact with the enterprise Security Gateway.
Multimedia
Applications such as video conferencing only work acceptably over low latency links that can offer the required minimum throughput. Currently on the Internet, latency and throughput can vary alarmingly. Multi-channel data services, such as ISDN and XDSL solve this problem in the short-term, allowing the "data" channel to be used for VPN tunneling, and a separate "voice" channel to be used for business telephone calls or video conferencing.
Encryption
When using encryption to protect a tunnel, data compression is no longer achievable as encrypted data is not compressible. This means that hardware compression over a modem connection is not possible.
Impact of Virtual Private Networks
The impact of VPN goes beyond secure and cost-effective remote access. Currently emerging security technology and public key infrastructure...
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now