++++++++++++++++++++++++++++++
|  NPING EXECUTION EXAMPLES  |
++++++++++++++++++++++++++++++

This document presents some examples of typical Nping executions, designed
by Brandon Enright.



+----------------------------------------------------+
| BASIC NPING                                        |
+----------------------------------------------------+

$ nping -v --tcp --syn -p 80 --count 2 www.google.com 

Starting Nping 0.0.1-SoC9 ( http://nmap.org/nping ) at 2009-05-11 22:34 UTC
NPING[2] www.google.com (66.102.7.99) with: TCP; flags: S; header: 40; data: 0

REPLY +14ms 66.102.7.99 with TCP; flags: SA; sport 80; ttl 53; rtt 14ms
REPLY +24ms 66.102.7.99 with TCP; flags: SA; sport 80; ttl 53; rtt 10ms

--- www.google.com nping statistic ---
2 packets tramitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 10/12/14 ms

Nping done: 1 IP address (1 host responded) pinged in 24ms






+----------------------------------------------------+
| BASIC NPING ECHO CLIENT                            |
+----------------------------------------------------+

$ nping  -v --client --channel-tcp 1337 --tcp --syn -p 80 --count 2  192.168.1.50

Starting Nping 0.0.1-SoC9 ( http://nmap.org/nping ) at 2009-05-11 22:34 UTC

------------------------------------------------------------
Connected to server on TCP 192.168.1.50:1638
------------------------------------------------------------
NPING[2] with: TCP; flags: S; header: 40; data: 0; ttl 64
REPLY +1ms 192.168.1.50 with TCP; flags: SA; sport 80; ttl 127; rtt 1ms
SERVER SAW 192.168.1.100 TCP; flags; S; header 40; data 0; sport 55322; ttl 63
REPLY +2ms 192.168.1.50 with TCP; flags: SA; sport 80; ttl 127; rtt 1ms
SERVER SAW 192.168.1.100 TCP; flags; S; header 40; data 0; sport 55323; ttl 63

--- 192.168.1.50 nping statistic ---
2 packets transmitted, 2 packets seen by server, 2 packets received 0% packet loss
round-trip min/avg/max = 1/1/1 ms

Nping done: 1 IP address (1 host responded) pinged in 31ms






+----------------------------------------------------+
| BASIC NPING ECHO SERVER                            |
+----------------------------------------------------+

$ nping --debug --server --channel-tcp 1337

Starting Nping 0.0.1-SoC9 ( http://nmap.org/nping ) at 2009-05-11 22:34 UTC

------------------------------------------------------------
Server listening for clients on TCP 0.0.0.0:1337
------------------------------------------------------------
[1] Client 192.168.1.100 connected with sport 36299
[1] Client reports NPING[2] 192.168.1.50:80 with: TCP; flags: S; header: 40; data: 0; ttl: 64
[1] Setting up receive filter "tcp dst port 80"
[1] Got probe[1]: TCP; flags; S; header 40; data 0; sport 55321; ttl 63
[1] Got probe[2]: TCP; flags; S; header 40; data 0; sport 55322; ttl 63
[1] Client 192.168.1.100 finished, disconnected
------------------------------------------------------------

--- server nping statistic ---
2 packets received, 2 packets expected, 0% packet loss

Nping done: 1 client connected. Server ran 100 seconds






+----------------------------------------------------+
| ADVANCED NPING ECHO CLIENT                         |
+----------------------------------------------------+

$ nping  -vv -d --client --channel-tcp 1337 --interpret --tcp --syn -p 80 --count 2 12.34.56.78

Starting Nping 0.0.1-SoC9 ( http://nmap.org/nping ) at 2009-05-11 22:34 UTC

------------------------------------------------------------
Connecting to Nping server TCP 12.34.56.78:1337...    [Done]
Establishing parameters...                            [Done]
Connected to Nping server on TCP 12.34.56.78:1337
------------------------------------------------------------
ECHO Server reports our public IP as 24.131.36.158
   [+] 24.131.36.158 not 192.168.1.100 : Could be behind NAT

NPING[2] with: TCP; flags: S; header: 40; data: 0; ttl 64
REPLY +1ms 12.34.56.78 with TCP; flags: SA; sport 80; ttl 120; rtt 90ms
SERVER SAW 24.131.36.158 TCP; flags; S; header 40; data 0; sport 35322; ttl 200
   [+] 24.131.36.158 not 192.168.1.100 : Could be behind NAT
   [+] sport 35322 not 55322 : could be behind PAT/NAT
   [+] TTL increased : expected decrease, something mangling packets?
   [+] DF bit set : is PMTU on?
REPLY +2ms 192.168.1.50 with TCP; flags: SA; sport 80; ttl 120; rtt 92ms
SERVER SAW 192.168.1.100 TCP; flags; S; header 40; data 0; sport 55323; ttl 63
   [+] 24.131.36.158 not 192.168.1.100 : Could be behind NAT
   [+] sport 35323 not 55323 : could be behind PAT/NAT
   [+] TTL increased : expected decrease, something mangling packets?
   [+] DF bit set : is PMTU on?

--- 12.34.56.78 nping statistic ---
2 packets transmitted, 2 packets seen by server, 2 packets received, 0% packet loss
round-trip min/avg/max = 90/91/92 ms

Nping done: 1 IP address (1 host responded) pinged in 300ms






