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
Npcap: Can it detect new interfaces without restarting the driver? #435
Comments
@dmiller-nmap Npcap seems to react in the same way as WinPcap and doesn't notice the network interface without a restart. |
@Varunram I agree with you. |
@dmiller-nmap , the Npcap/WinPcap driver is never a plug-and-play driver. Technically, there are two difficulties:
IMHO, maybe having this feature would be fancy, but restarting the driver after installing a new interface just seems also good enough. |
It would be great to have a better solution to this going forward. |
@dmiller-nmap |
Npcap 0.9983 fixes this issue: adapters can be detected and supported for capture and injection as soon as they are bound to the NDIS stack! |
Thread on WinPcap-users mailing list: https://www.winpcap.org/pipermail/winpcap-users/2017-January/005025.html
The user notes that WinPcap cannot detect new plug-and-play interface until the computer is rebooted. Another user comments that simply restarting the
npf
driver service will accomplish the same thing.I would like to know whether Npcap has the same behavior or if this is solved with the new filter driver design. If it has the same behavior, we should investigate what it might take to detect new interfaces without restarting the driver.
The text was updated successfully, but these errors were encountered: