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

Port RTT Measurements #1362

Open
mcordingley opened this Issue Oct 19, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mcordingley

mcordingley commented Oct 19, 2018

From digging through the docs and some historical mailing list messages, it looks like nmap doesn't currently support reporting RTT times for individual ports.

  1. Could you please add port RTT times to the output somehow? For what it's worth, I'm currently using the -oX option to feed other scripts. Unfortunately, I don't know C and therefore cannot submit a patch for this. If dev time is a constraint, I'll gladly trade some Web dev time to help make this happen.
  2. Until this is a feature or if this never becomes a feature, is there some alternate way that I could get this timing information? I'm currently calling nc in a loop, but that runs serially. The run time simply doesn't scale for the level of network monitoring that I'm trying to do.

Thanks!

@dmiller-nmap

This comment has been minimized.

dmiller-nmap commented Oct 22, 2018

Nmap doesn't keep this information internally, so there's no easy way to output it. However, there is a NSE script that calculates round-trip times for each port as a way of distinguishing forwarded ports on a NAT interface. It's called qscan.

@mcordingley

This comment has been minimized.

mcordingley commented Oct 22, 2018

Thanks for that link. I'll give it a look and remember it for future work. I ended up wrapping the functionality I needed into a Python script, as I discovered that it can run parallel processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment