Which protocol is better?

[piperent]

Given the following scenario, which VPN protocol would best fit the situation?

I have a Local Unix and a Remote Unix server which perform un-attended file transfers between each other during the evening. On the Local side, I also have PC's that connect to the Remote as terminal emulators just to perform some simple application input functions thru-out the day. Currently they are using a simple dial-up connection to perform all of this (uucp at night thru dial-up, and dial-up connection during the day for logging in). Let me clarify, both Unix machines run in character mode ONLY (no X-desktop, no internet connectivity, no samba, etc) but are full enterprise machines with networking configured for all in-house users.

I have a few sites which are using VPN clients over IPsec VPN tunnels, and I find that they are very difficult (practically impossible) to setup and/or maintain. Is SSL VPN a plausible solution, or is a hardware VPN solution (router to router) my only option? I guess what I am looking for is a configurable, maintainable VPN connection that can handle UUCP (or tftp), and remote terminal emulation over the web.

I'd be happy to hear from some others on how they have resolved similar situations.


As always, any information will be greatly appreciated.

Thanks,
JP

 

[brianinms]

When properly configured VPNs are a set it and forget it proposition. I would recommend you look at a hardware based solution such as Cisco ASA's or sonicwall firewalls.

 

[piperent]

Thanks Brianinms for the input. I was sort of leaning in that direction, but have been hearing a lot about the SSH tunnels and am still wondering how functional something like that would be. But with no hands-on experience with them, I really don't want to be in a learning mode at my client's expense.

I appreciate you.

JP

 

[burtsbees]

IPSec is more secure than SSH, because the info is hidden in the tunnel and IPSec offers 3DES, which is stronger than ssh 1 or ssh 2.

Burt