|
|
The latest few versions of OpenVPN try to implement the --ifconfig options on Windows, just like it works on Linux and and every other platform. --ifconfig basically tells OpenVPN to set the TCP/IP properties (i.e. network and subnet mask) on the TAP adapter programmatically. The problem is that while Windows has quite a number of different ways to do this, each method seems to work great on one version of Windows while breaking down completely on another. The latest version of OpenVPN has an option --ip-win32 which lets you choose one of three methods for setting the IP address. The newest method is "ipapi" which uses the Windows "IP helper API". I would like to get some feedback on the "ipapi" method, specifically cases where it does and doesn't work. A few pointers on ipapi: * It's best to use it on TAP-Win32 adapters in their original state, with no fixed IP or netmask, and "Obtain an IP Address Automatically" checked. * If you get an error, (a) try disabling and renabling the driver in the network control panel, or (b) try adding a "tap-sleep 15" option which will cause OpenVPN to sleep for 15 seconds after it opens the TAP adapter to give it time to get connected. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |