I’m trying to answer the question that was asked in the “Getting Started > Service Scanning” module.
I need to perform nmap -p- <IP>, which is taking too long.
I’ve tried restarting the lab and my VPN multiple times, even using the -T 3 flag, but the speed has remained the same.
the module is teaching us nmap, I don’t see any reason to use an alternative such as Rustscan. However, I’ve seen its very good performance.
Thanks for sharing
The T flag regarding the speed the packets sent. -T 3 is not that fast. -T 4 is reasonable but not always correct.
Use the following flags to force your tool to send less packets, therefore, scan faster:
-Pn
--min-rate 9327 or 3000 by UDP scan
You can use nmap -h to figure out why those flags are useful.
reading nmap’s docs (#rtfm) it looks like you would like to check those 2 flags for scan:
– -max-retries (with 1?)
– min-rate 120 (windows?)
Also: in this (kind of) case (you’re talking about) I’ll try to check ‘fast default portscan’ (so -F) and then try to ‘specify’ the ‘range’ I’m lookking for.
Don’t scan all the ports at once. I think some kind of timeout works on the machine to prevent scanning a large number of ports at once. Scan 1500 ports at once. Then the next block of 1500 and so on. Anything more than 1500 and it would start taking longer. That is how I got around this timeout.