Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question, can we install/add or update a single interface without affect other interfaces? #227 #130

Open
lygstate opened this issue Sep 26, 2020 · 1 comment

Comments

@lygstate
Copy link

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

@selvanair
Copy link
Collaborator

selvanair commented Sep 26, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants