Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We've had numerous support hassles with software VPN clients.

Our remote devs need to connect to a number of different customer VPNs. Are there any reasonably priced VPN client boxes we could supply for them to use in their SOHO settings - so that they wouldn't need to get VPN client software working on their machines?

We need something that is flexible enough to work with common VPN servers - as we won't always be controlling that side of the connection.

share|improve this question

closed as off-topic by Falcon Momot, Tom O'Connor Jul 10 '13 at 9:38

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions about hardware or software used in a home setting are off-topic because they require answers that may not be practical for the business and support professionals here. You should try asking on Super User instead." – Tom O'Connor
If this question can be reworded to fit the rules in the help center, please edit the question.

IME if you can't control both ends of a VPN then don't expect much success. IPSEC appeared to be a god send for solving these problems - but by the time it got implemented where were just too many different ways to configure it - even if you get your implementations from the same source.

Although there are relatively cheap off-the-shelf units which are straightforward to implement in a planned network - this approach does not scale down to SOHO installations where the internet connection may be via a modem which requires client software/non ethernet connection to the client device or a router which implements masquerading.

Have you tried using openvpn? Software will run on every flavour of Unix/Linux/POSIX including MacOSX and Microsoft NT based kernels, uses SSL so easily crosses NAT.

(note: SSL tunneling does have additional overheads which you don't have with IPSEC, however I've previously run VOIP over SSL based VPN - before openVPN was as mature as it is now - and had no detectable problems with jitter / frame loss, bandwidth overhead was relatively low too. I've not run OpenVPN over such a large network but given the same underlying technologies I wouldn't expect any issues)

share|improve this answer
    
+1 for OpenVPN. We use it a lot and it works a charm. Easy to configure, can easily handle multiple configurations for connections to a variety of targets. Plus: you can test a config for a particular connection, then simply mail it to everybody who needs to connect, with simple instructions on what to change (if anything). Recipient pops the config file into a specific folder, and Bob's your uncle. – wolfgangsz Aug 30 '10 at 13:28

Not the answer you're looking for? Browse other questions tagged or ask your own question.