-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Nmap 6.49BETA4 - unable to find right interface to send packets #191
Comments
We run into this problem on occasion when Linux kernel adds a new ARP_HRD_* constant. See the Nmap modifications to libdnet for examples of previous fixes. Unfortunately, it's often hard to pin down what constant needs to be added. I tried to write a diagnostic program to get this info, but it has yet to be successful. If you could try it out or figure out a better way, that'd be great. It's attached to this message on the nmap-dev mailing list: https://seclists.org/nmap-dev/2015/q2/165 |
nmap does not work when running as root for me. In case it helps, the diagnosis program you posted shows this:
CentOS with some run off the mill networking PC with kernel 3.10.0-957.27.2.el7.x86_64. The network output I cannot write up here, but it has some 5 Intel NICs and 2 WAN modems. |
any update about this issue? |
I don't know 😕 buy still I am getting the error |
This problem was orginally submitted at my NetworkMapper project here:
kost/NetworkMapper#6
But, I see it more as Nmap binary problem itself as nmap binary is reporting this.
Nmap is not able to find right interface to send packets. Actually it cannot find any interfaces:
cannot find interfaces on:
More about the problem:
kost/NetworkMapper#6
The text was updated successfully, but these errors were encountered: