Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Make nping output more like Unix ping?
From: "Luis MartinGarcia." <luis.mgarc () gmail com>
Date: Tue, 17 Sep 2013 22:18:44 +0200

Hi, Jacek.

Sorry for the late reply. I do understand your need to quickly see the
RTT but unfortunately nping does not offer that possibility yet. Of
course it offers RTT statistics at the end but at this moment there is
no way to see RTTs displayed in the RECV packet output line.

I'll make a note about your request and add it to the to-do list.

Best regards,

Luis MartinGarcia.



On 09/08/2013 12:26 AM, Jacek Wielemborek wrote:
Hi,

Here's an example output for my university's students' SSH server, pinging HTTP:

[d33tah-laptop][~] $ nping kolos.math.uni.lodz.pl

Starting Nping 0.6.40 ( http://nmap.org/nping ) at 2013-09-08 00:16 CEST
SENT (0.0072s) Starting TCP Handshake > kolos.math.uni.lodz.pl:80
(212.191.65.66:80)
RECV (0.0147s) Handshake with kolos.math.uni.lodz.pl:80
(212.191.65.66:80) completed
SENT (1.0113s) Starting TCP Handshake > kolos.math.uni.lodz.pl:80
(212.191.65.66:80)
RECV (1.0212s) Handshake with kolos.math.uni.lodz.pl:80
(212.191.65.66:80) completed
SENT (2.0132s) Starting TCP Handshake > kolos.math.uni.lodz.pl:80
(212.191.65.66:80)
RECV (2.0209s) Handshake with kolos.math.uni.lodz.pl:80
(212.191.65.66:80) completed
SENT (3.0165s) Starting TCP Handshake > kolos.math.uni.lodz.pl:80
(212.191.65.66:80)
RECV (3.0255s) Handshake with kolos.math.uni.lodz.pl:80
(212.191.65.66:80) completed
SENT (4.0183s) Starting TCP Handshake > kolos.math.uni.lodz.pl:80
(212.191.65.66:80)
RECV (4.0271s) Handshake with kolos.math.uni.lodz.pl:80
(212.191.65.66:80) completed

Max rtt: 10.014ms | Min rtt: 6.828ms | Avg rtt: 8.498ms
TCP connection attempts: 5 | Successful connections: 5 | Failed: 0 (0.00%)
Nping done: 1 IP address pinged in 4.03 seconds

When I run "ping", it the example output looks like this:

[d33tah-laptop][~] $ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=44 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=44 time=40.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=44 time=43.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=44 time=42.0 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 40.180/41.544/43.373/1.299 ms

I like this kind of output, because it clearly shows me how the RTT
changes over time and lets me decide when I saw enough data. While I
can run nping -c 0, I cannot find an option to display RTTs for every
request. Is there a way to make nping -H show me how much time passed
between sending the last packet and receiving the response so I could
tell at a glance when the responses slowed down and how much?

Yours,
Jacek Wielemborek
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]