Eric Newberry | 7f25a11 | 2015-05-31 11:23:25 -0700 | [diff] [blame] | 1 | # ndnping and ndnpingserver |
| 2 | |
| 3 | ## Introduction |
| 4 | |
| 5 | **ndnping** and **ndnpingserver** are reachability testing tools for |
| 6 | [Named Data Networking](http://named-data.net). They test the reachability between two nodes. The |
| 7 | client sends an Interest intended for a node running **ndnpingserver**. The ping server then sends |
| 8 | Data in response. The client then calculates the roundtrip time for the Interest-Data exchange, or |
| 9 | marks it as a timeout if the Data is not received within the timeout period. |
| 10 | |
| 11 | ## Using the Client |
| 12 | |
| 13 | The client can be invoked by calling **ndnping** with a name to ping. For example, to ping |
| 14 | `ndn:/edu/arizona`, one would execute:: |
| 15 | |
| 16 | ndnping ndn:/edu/arizona |
| 17 | |
| 18 | There are also a variety of options to control the behavior of the ping client. For example, to |
| 19 | send only four pings to `ndn:/edu/arizona`, displaying a timestamp with each received Data or |
| 20 | timeout, type:: |
| 21 | |
| 22 | ndnping -c 4 -t ndn:/edu/arizona |
| 23 | |
| 24 | A list of the available options can be found with `man ndnping`. |
| 25 | |
| 26 | ## Using the Server |
| 27 | |
| 28 | The server can be invoked by calling **ndnpingserver** with a name to listen for pings to. For |
| 29 | example, to listen for pings to `ndn:/edu/arizona`, one would execute:: |
| 30 | |
| 31 | ndnpingserver ndn:/edu/arizona |
| 32 | |
| 33 | There are also a variety of options to control the behavior of the ping server. For example, to |
| 34 | satisfy only 4 ping requests before exiting, execute the following:: |
| 35 | |
| 36 | ndnpingserver -p 4 ndn:/edu/arizona |
| 37 | |
| 38 | A list of the available options can be found with `man ndnpingserver`. |