Changes between Version 14 and Version 15 of TesterDocumentation


Ignore:
Timestamp:
08/11/11 19:26:55 (13 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TesterDocumentation

    v14 v15  
    4747}}}
    4848
    49 = Debugging =
     49= TAP-driver debugging =
     50
     51Occasionally you may have to try out different versions of the Windows TAP-driver. This can be done with ''<openvpn-install-dir\bin\tapinstall.exe''. This tool is actually renamed [http://support.microsoft.com/kb/311272 Devcon.exe].
     52
     53It's fairly straighforward to use ''tapinstall.exe'' from a command-prompt. The <id> is an identifier which ''tapinstall.exe'' uses to detect the correct driver. In case of OpenVPN 2.2* it's ''tap0901''. This may be different in older/newer versions. To view information about an installer driver use
     54
     55{{{
     56$ tapinstall.exe hwids <id>
     57}}}
     58
     59To uninstall a driver use:
     60
     61{{{
     62$ tapinstall.exe remove tap0901
     63}}}
     64
     65To install a new TAP-driver use
     66
     67{{{
     68$ tapinstall.exe install <something.inf> <id>
     69}}}
     70
     71It's also possible to [wiki:BuildingOnWindows#ExtractingsignedTAP-driversfromanOpenVPNinstaller extract TAP-drivers from OpenVPN installer] without installing OpenVPN.
     72
     73= OpenVPN Debugging =
    5074
    5175If OpenVPN crashes, you can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the ''openvpn debug'' and ''gdb'' packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this: