You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when more and more tap interfaces are created, the creating procedure are slower and slower cause everytime creating interface, it's would affect all interfaces
The text was updated successfully, but these errors were encountered:
If all exisitng adapters use the same driver as the one selected for the new one, previous adapters are not restarted. In other words, a running tunnel should not get interrupted. This is how tapctl.exe installs it (at least as in ~ beta4 and later). Driver update is done during the msi installation.
If you use tapinstall (or devcon), the driver is selected using the inf file on command line and its forced -- meaning existng adapters are restarted as the driver may change. The restart happens even if the driver does not really change. That will cause an interruption of any active tunnels.
That said, in both cases windows does an enumeration of existing adapters to decide a device restart is required or not, and this could be slow. We're just using the driver setup API.
Like through registry or other means?
Currently, when more and more tap interfaces are created, the creating procedure are slower and slower cause everytime creating interface, it's would affect all interfaces
The text was updated successfully, but these errors were encountered: