search

OpenVPN / tap-windows6

Windows TAP driver (NDIS 6)
Other
798 stars 237 forks source link

I do change version.m4 and build successfully, but it seems to collide with the original network interface driver #123

Closed DaDaQingFeng closed 4 years ago

DaDaQingFeng commented 4 years ago

If the original network interface driver existed, I can't manage to install my driver~ Do I need to modify like ClassGUID sort of things?

selvanair commented 4 years ago

Depends on what you want to do. If you are just updating the tap-windows6 driver with your own version, changing the version number and date should be enough. The tapctl.exe utility always selects the "best" driver in the store, but you can force any version using devcon (or tapinstall).

Or see the description in README.rst on quickly testing changes without having to update the version.

But, if the aim is to create a separate set of adapters that could co-exist with tap0901 adapters with independent drivers, you have to do more. Essentially the hardware id (tap0901) should be changed as all device nodes with same hwid will get the same driver. Read the "note to developers" section in the inf file.

Do not change the class GUID as that is of the NET class the driver belongs to.

DaDaQingFeng commented 4 years ago

Depends on what you want to do. If you are just updating the tap-windows6 driver with your own version, changing the version number and date should be enough. The tapctl.exe utility always selects the "best" driver in the store, but you can force any version using devcon (or tapinstall).

If you want to create a separate set of adapters that could co-exist with tap-windows6 adapters with independent drivers, you have to do more. Essentially the hardware id should be changed as all device nodes with same hwid will get the same driver. Read the "note to developers" section in the inf file.

Do not change the class id as that is of the NET class the driver belongs to.

much obliged!