Closed Twigonometry closed 3 years ago
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. are you sure the host has open ports?
Hi,
The host is up and has open ports, as I scanned it manually with the -Pn
flag and 3 open ports were found (see original comment for command output)
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 997 filtered ports
text (meaning 3 are open). Sorry for any confusion
This same issue is occurring for me. I vote it be reopened.
If I run my port scan with sudo
, SYN scan returns results.
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!