XPost: comp.dcom.sys.cisco, comp.os.linux.networking, microsoft.   
   ublic.windows.server.networking   
   From: david@westcontrol.removethisbit.com   
      
   Dave Warren wrote:   
   > In message    
   > Stefan Monnier  was claimed to have wrote:   
   >   
   >>> OpenVPN is proprietary and will not work with a Draytek router.   
   >> In which sense is OpenVPN proprietary?   
   >   
   > In the sense that OpenVPN built their own protocol rather than relying   
   > on one of the existing standards.   
   >   
   > There is a lot I like about OpenVPN, but the client side stuff is just   
   > downright nasty to configure, maintain, or even use.  It's great for   
   > techies, but I couldn't imagine putting it in front of an end user.   
      
   I would say the same thing about any VPN solution other than OpenVPN.   
   For the most part, we have windows clients and linux servers.  When   
   someone needs OpenVPN access, I just give them a copy of the windows   
   installer, and generate a key and a configuration file (which is simply   
   a sample config file with the remote address modified appropriately).   
   The setup is vastly easier than other ways to handle VPNs, especially if   
   the client is behind a router or needs to connect to multiple VPNs.   
      
   In other cases, we've provided routers with OpenWRT installed and the   
   client configured.  The user plugs in the router, and has VPN access via   
   one of the network ports.  It couldn't be easier.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)