Skip to content
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

[Feature Request] Timing related parameters monitoring #1620

Open
AresS31 opened this issue Jun 6, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@AresS31
Copy link

commented Jun 6, 2019

I found out that no matter how high the debugging or verbose levels are set, there is currently no way to monitor the values of dynamic parameters such as --min-parallelism, --max-parallelism at runtime.

As far as I know, the -d switch can be added to an nmap command in order to display the values of the timing parameters that will be used during the scan, however, these values are being displayed only once and at the start of a scan, as shown in the following output.

--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 1000, min 100, max 10000
  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
  parallelism: min 0, max 0
  max-retries: 10, host-timeout: 0
  min-rate: 0, max-rate: 0
---------------------------------------------

Adding a new interactive keystroke/option (e.g. s for status or t for timing) to the already present ?, d/D, v/V keystrokes/options would be very useful, especially in my current situation where I am limited by a client to a hard limit of 30K concurrent sessions/connections open at the same time.

This could allow me to interactively query nmap to instantly get an updated version of the above text output and help me decide whether I should manually set the value of the --max-parallelism parameter which would obviously negatively impact the speed of my scans. Thus, adding the requested feature would help me make a choice.

@AresS31 AresS31 changed the title [Feature Request] Monitor dynamic timing parameters at runtime [Feature Request] Timing related parameters monitoring Jun 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.