RomanNum3ral
/
AutoRecon
mirror of https://github.com/Tib3rius/AutoRecon.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Frequently Asked Questions (markdown)

Tib3rius 2022-01-09 20:55:07 -05:00
parent c91beefde4
commit 78d2872497
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Frequently-Asked-Questions.md

@ -8,4 +8,12 @@ It is entirely possible that one command (usually a full TCP Nmap scan or direct
The port scans are performed using Nmap, which tries to be "safe" when scanning by not flooding the network with large amounts of packets. There is always a trade off between speed and accuracy when it comes to port scanning. However, this does mean that by default, Nmap can be slow. AutoRecon does run Nmap with `-T4` which is the second highest "timing template" available, which should increase the speed, however it doesn't go beyond that.
Luckily, one of the core principles of AutoRecon v2 is that users should be able to easily configure commands to their liking. As a result, there is an `--nmap-append` command line option, which allows the user to pass extra arguments to every Nmap command. For example, you could run AutoRecon with `--nmap-append="-T5"` to use the fastest timing template, or even set `--nmap-append="--min-rate=5000"` which tells Nmap to send at least 5000 packets per second.
Luckily, one of the core principles of AutoRecon v2 is that users should be able to easily configure commands to their liking. As a result, there is an `--nmap-append` command line option, which allows the user to pass extra arguments to every Nmap command. For example, you could run AutoRecon with `--nmap-append="-T5"` to use the fastest timing template, or even set `--nmap-append="--min-rate=5000"` which tells Nmap to send at least 5000 packets per second.
# Why did AutoRecon miss <insert port/service here>?
The short answer: it didn't.
The long answer: AutoRecon doesn't do any port scanning itself, it relies on other programs like Nmap. So Nmap missed the port/service. Why did that happen? Well, it could be multiple reasons. Maybe the network got flooded with packets and responses didn't get returned, maybe the port/service wasn't up when it was scanned, etc.
You should not rely on just one tool for enumeration either. If you have time, run multiple Nmap scans. If you find ports that AutoRecon didn't, you can always re-run AutoRecon with the `-p` command line option and a comma separated list of ports for it to scan.