-
Notifications
You must be signed in to change notification settings - Fork 59
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
Is Npcap with Winpcap compatible API expected? #302
Comments
Installing Npcap doesn't enable its service by default.
If Npcap's state is STOPPED, then it must be started in an Administrator command prompt.
In my experience, the service persists after shutdown and restarts. Also, remember to launch ACT and load the plugin before logging in. |
Running Additionally, is there something about ACT that requires this extra step that Wireshark or other programs may not need? Not sure what the difference is with what I did to make it work there (between enabling the compatibility and not adding it to Npcap). If the service is required to be running for it to work, I'm unsure how what I did does work. |
What operating system are you running, then? Or did you get a message along the lines of the service not existing at all? |
Windows 10 (10.0.19045). No output at all, see below. Tried on both admin and non admin prompt, Npcap 1.72 is the version I'm using if it helps.
|
Trying to get this working without running as administrator, I noticed the UI will not detect any interfaces for inspecting traffic. Errors pop up indicating that Winpcap or Npcap must be installed, even though I have Npcap installed. I selected "Use Winpcap compatible library" in the settings but that made no difference. Looking at debugs, only mention of Winpcap existed in them.
I was able to get this running by reinstalling Npcap with an additional option, a Winpcap compatible API mode. Is this expected behavior?
The text was updated successfully, but these errors were encountered: