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
wireshark lost traffic capture to loopback after upgraded npcap 0.99-r5 #384
Comments
Same problem. |
Same problem. |
Thanks for the bug report. The usual cause of this problem is installing Npcap in WinPcap API-compatible mode, which makes Wireshark unable to capture loopback traffic. However, @timeregained's DiagReport output does not seem to show that configuration. We will investigate further. @timeregained Does the problem happen if you follow this procedure to completely remove all Npcap Loopback Adapters on your system? https://github.com/nmap/nmap/issues/923#issuecomment-402258775 |
@dmiller-nmap Yes, the problem is still there after completely removing all Npcap Loopback Adapters on my system. By the way, the npcap is installed in WinPcap API-compatible mode and I still need this mode because some apps still depend on WinPcap. |
@timeregained Thanks for the reply. I would usually close this at this point, since it's a known issue that Wireshark does not use Npcap properly when WinPcap API-compatible mode is installed, but since you say that 0.99-r2 did work, I'll spend a bit more time investigating. |
Ok, this issue is due to an incomplete fix for nmap/nmap#1165. We made sure that when |
FixInstall.bat does not help.
|
@ExIngus Can you provide output from DiagReport.bat and |
LoopbackSupport REG_DWORD 0x1 |
@ExIngus I still can't tell what's going wrong there. Delete the |
Recently I have upgraded npcap to 0.99-r5, however , wireshark cannot capture the loopback traffic anymore, I have downgraded npcap to the version 0.99-r2 which is distributed with nmap 7.70 and it works.
Log of DiagReport and NPFInstall have been uploaded as following:
DiagReport-20180511-091823.txt
NPFInstall.log
The text was updated successfully, but these errors were encountered: