Installing virtual network adapter

wodVPN ActiveX Control - Installing virtual network adapter

wodVPN is shipped with 'WeOnlyDo Network Adapter' that can be used (and distributed) royalty free by your applications. It is neccessary if you plan to use wodVPN's capability to route all network traffic between peers. You can also use virtual network adapter provided by Wippien (http://wippien.com) or OpenVPN (http://openvpn.net). Please check their respective license agreements for usage and distribution of their adapters.

Same usage rules in wodVPN are applied for all adapters. Only one adapter can be used at a time by wodVPN.

Installing the adapter

When installed using our setup package, adapter will be automatically installed. If you plan to distribute the adapter, you will need 4 files we provided for you:

    wod0205.sys (system driver binaries)
    wod0205.cat (driver catalog file)
    OemWin2k.inf (driver installation file)
    DrvInst.exe (driver installer)

Copy those files to destination system, and do the following:

to install adapter: DrvInst install OemWin2k.inf
to uninstall adapter: DrvInst uninstall

You will need administrative privileges on remote system to do so!

Setting up the adapter

When installed, you should set IP address and Netmask for the adapter (right-click on the adapter, select Properties) in the same range as the adapter of the remote wodVPN peer. If you try to use adapter without setting the IP/Netmask combination (such as, if you leave it on DHCP) wodVPN will failed to work with it.

You can also use 3rd party tools to set IP/Netmask, or can use 'netsh.exe' that is provided with all Windows installations. You will need to call this tool as external process, typically in this form (make sure you have administrative privleges!):

interface ip set address name="WeOnlyDo" static 192.168.1.1 255.255.255.0

where 'WeOnlyDo' is name of the adapter - we set it to that name during installation. On some systems it may appear as 'Local Area Connection xyz', it's up to you to use correct name - check out VPNInterface.Name property to see what is the correct one. '192.168.1.1' is new local IP address, and '255.255.255.0' is new netmask to be set. Netsh will execute for few seconds, so you may want to wait for process to finish (it's up to you to determine how to do that) before you can start using the adapter in your application with new values.