-
Notifications
You must be signed in to change notification settings - Fork 802
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
Recon scan does not trigger ping scan being disabled #57
Comments
this doesn't appear to be a bug. The host simply doesn't have any ports open, so the script can't run anything on it. |
Hi, The host is up and has open ports, as I scanned it manually with the The host does not respond to ping probes, but nmap automator doesn't recognise this for some reason. From looking at the source code it seems like it should display a message saying the host is not responding to ping probes, which doesn't show up in the terminal output. Edit: I had removed which ports are open from my original comment as I'm not supposed to share those details, so it may have been hard to spot - but the number of open ports can be seen by the |
If I run my port scan with |
Using fresh install, with
ffuf
installed (no Gobuster but instructions say I could use one or the other).Running the following command, it says no ports were found:
Here is the output, suggesting the host is down:
Running
nmap
manually with the-Pn
flag shows the host is up:So the script does not seem to pick up on the fact the host is down then re-run the scans with
-Pn
Thanks!
The text was updated successfully, but these errors were encountered: