1
0
mirror of https://github.com/nmap/nmap.git synced 2026-01-06 14:39:03 +00:00
david b5b558f162 Don't use the clobbered rtmsg->rtm_family to look up interfaces.
This value gets clobbered after the netlink recvmsg. It was giving me a
bogus address family (234), which caused the call to getInterfaceByName
to fail:
Could not find interface wlan0 which was specified by -e

This seems to have been exposed by r29754. Specifying a source address
that is not on any actual route seems to result in a netlink query
result with 0 entries, and the changed value of rtm_family. (The fact
that there are no routes returned is not a problem, because we bail out
early when -e is given, now that getInterfaceByName works again.)
2012-09-11 23:50:21 +00:00
2012-09-08 16:22:23 +00:00
2012-08-02 18:35:36 +00:00
2012-09-08 19:44:24 +00:00
2012-09-10 21:03:17 +00:00
2012-09-10 23:53:54 +00:00
2012-03-07 03:15:51 +00:00
2012-09-08 19:44:24 +00:00
2012-05-27 08:53:32 +00:00
2012-03-07 17:59:55 +00:00
2012-08-28 08:20:31 +00:00
2012-08-28 07:50:09 +00:00
2012-08-03 23:46:06 +00:00
2012-08-28 13:07:19 +00:00
2012-05-27 08:53:32 +00:00
2008-07-31 14:18:21 +00:00
2012-05-27 08:53:32 +00:00
2012-05-27 08:53:32 +00:00
2012-05-27 08:53:32 +00:00
2012-08-04 16:05:24 +00:00
2012-05-27 08:53:32 +00:00
2012-05-27 08:53:32 +00:00
2012-05-27 08:53:32 +00:00
2012-05-27 08:53:32 +00:00
2012-08-28 07:50:30 +00:00
2012-03-19 16:48:27 +00:00
2012-08-14 16:36:25 +00:00
2012-08-14 16:36:25 +00:00
2012-05-05 18:02:34 +00:00

Here is some documentation for Nmap, but these files are much less
comprehensive than what you'll find at the actual Nmap documentation
site ( http://nmap.org ).
Languages
C 37.8%
Lua 28.1%
C++ 16.7%
Shell 5.8%
Python 4.2%
Other 7.2%