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

npcap should use libpcap 1.9.0 #313

Closed
guyharris opened this issue Mar 7, 2019 · 4 comments
Closed

npcap should use libpcap 1.9.0 #313

guyharris opened this issue Mar 7, 2019 · 4 comments

Comments

@guyharris
Copy link
Contributor

The current Npcap 1) appears to build remote capture support but 2) that support doesn't work - see, for example, this ask.wireshark.org question, this Wireshark bug, and the-tcpdump-group/libpcap#795.

Libpcap 1.8.x's remote-capture support had a number of bugs; 1.9.0 was the first release where it was reasonably usable (even on Windows, much less on UN*Xes).

Please upgrade to libpcap 1.9.0 (and let us know what changes you need to apply, and why).

@dmiller-nmap
Copy link
Contributor

Looks like we'll get this included in the next release. Had some difficulty due to this libpcap issue: the-tcpdump-group/libpcap#810

@guyharris
Copy link
Contributor Author

So shall we close this?

@dmiller-nmap
Copy link
Contributor

Yeah, should be fine. We often keep issues open until release when we need confirmation from the original reporter, but this is straightforward.

@guyharris
Copy link
Contributor Author

Wireshark bug 15547, which reported that remote capture wasn't working with Npcap, now has a user who said "I have the same problem" saying that remote capture is working with npcap v0.992.

@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