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

No flow preview in Wireshark 3.0.3 after install npcap 09981 #342

Closed
tan-wei opened this issue Jul 25, 2019 · 4 comments
Closed

No flow preview in Wireshark 3.0.3 after install npcap 09981 #342

tan-wei opened this issue Jul 25, 2019 · 4 comments

Comments

@tan-wei
Copy link

@tan-wei tan-wei commented Jul 25, 2019

As the image shown below, the flow preview curve is flat after install npcap 09981 intead of npcap 0995. It's not correct, because many packets are sent and received now.
图片
It's quite wired that I try to uninstall npcap 09981 and install npcap 0995, no interfaces are shown in wireshark.

@dmiller-nmap
Copy link
Contributor

@dmiller-nmap dmiller-nmap commented Jul 25, 2019

Thanks for reporting this. I believe there may be a regression in packet statistics reporting, so I will be looking into that, assuming that is how these flow curves are generated.

@dmiller-nmap
Copy link
Contributor

@dmiller-nmap dmiller-nmap commented Jul 25, 2019

Additionally, if this is important enough of an issue that you wish to install an older version of Npcap, please use Npcap 0.996, since there is a significant bug in 0.995 that can crash Windows. Older versions are available at https://nmap.org/npcap/dist/?C=M;O=D

@dmiller-nmap
Copy link
Contributor

@dmiller-nmap dmiller-nmap commented Jul 25, 2019

Thanks so much for the fast report! Since we changed IOCTL codes in 0.9981, the IOCTL for getting packet statistics was using the wrong I/O method. This will be fixed in the next release. We will be adding additional tests to ensure packet stats functionality works correctly in all future releases. Thanks again!

@tan-wei
Copy link
Author

@tan-wei tan-wei commented Jul 25, 2019

Thanks for the quick reply. I think I can wait for the new release which can fix this bug. :-)

@fyodor fyodor transferred this issue from nmap/nmap May 5, 2021
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