-
-
Notifications
You must be signed in to change notification settings - Fork 457
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
Hostname sweep throws an exeption when using 100.100.x.x target range #1
Comments
Could you post the command line arguments that you used? Also could you confirm the version of nmap that you have installed? |
Sorry, I just missed that command line, and I updated my contents. |
Could you attempt an update of nmap and see if it resolves the issue? Nmap should support hostnames in the target specification (source: https://svn.nmap.org/nmap/docs/nmap.usage.txt) however I can't verify that for your particular version. Alternatively, if you use the ip address for the host it should work fine. You could also specify a range with something like:
Or if you just want to target the machine hdp01 and know the ip address (for example) is 192.168.0.32 you would use:
Note that I removed the ping sweep and dns flags as they would be redundant in the case of a single host. |
I got same errors to two-versions command parameters. |
To clarify - you tried using the ip address as the target instead of the hostname to reproduce the issue? Could you paste your terminal output here? |
[flamingo@flamingo reconnoitre]$ ll [#] Identifying hostnames |
Ok great, makes sense now. It looks like a bug in the way the arguments parser handles input for the target (.x.x specifically). I can look at a patch or potentially a pull request on the parser library but in the meantime you'll need to specify the full ip address (or specify the range like I did above). I'm midway through my lab journey so it may be a couple of days until I can update this thread further, feel free to nudge me if this stays open too long. |
Actually, no sorry, I'm wrong. The error is in the hostname_scan (can't believe I took this long to notice!). Do you have nbtscan installed? The following will do everything but a hostname scan for you in the meantime:
|
Yes, when I executed second command what you said, and then I found nbtscan command not found in terminal, so I got nbtscan-1.5.1-1.2.el6.rf.x86_64 package from another epel6 link, and installed it additionally. |
Great! I've updated the readme to mention both tools and I'll add some exception handling to the entry point for these functions in the future to check for these dependencies before executing. |
One more thing, snmpwalk package is required to use that command with --snmp option.
|
You're right - I'll have to wrap some exception handling into it! Wasn't really intended for wide use outside of Kali. |
When I exectued reconnoitre.py with other .py in this package, I got these errors.
OS : CentOS 6.8
Python Version : 3.5.1
Command Line : python reconnoitre.py -t hdp01 -o /data/user/flamingo/workflow/python/v3/reconnoitre/output --services --pingsweep --dns --hostnames --snmp
File "reconnoitre.py", line 65, in
main();
File "reconnoitre.py", line 47, in main
ping_sweeper(arguments.target_hosts, arguments.output_directory, arguments.quiet)
File "/data/user/flamingo/workflow/python/v3/reconnoitre/ping_sweeper.py", line 19, in ping_sweeper
lines = results.split("\n")
TypeError: a bytes-like object is required, not 'str'
The text was updated successfully, but these errors were encountered: