$(Title)
- -<> - - - -- -
- -echoping is managed by Stéphane Bortzmeyer -
<bortz@users.sourceforge.net>. echoping assumes the remote host accepts such connections. Experience show that -most Internet routers do and many hosts also. However, some Unices are not -shipped with this service enabled and, anyway, the administrator is always -free to close it (I think they shouldn't). echoping has therefore less chance -to succeed than ping or bing. (On a typical Unix box, "echo" service is -configured in /etc/inetd.conf but see the CERT advisory.) - -
echoping simply shows the elapsed time, including the time to set up the TCP -connection and to transfer the data (but excluding the time for the -- possible - DNS call). Therefore, it is unsuitable to physical -line raw throughput measures (unlike bing). On the other end, the action it -performs are close from a HTTP request and it is meaningful to use it -(carefully) to measure Web performances. - -
With UDP servers you can have surprises: the first test is quite often -much slower since inetd has to launch the process. After that, the process -stays a while so the next texts run faster. - -
There are many, many traps when measuring something on the Internet. Just one -example: 'echoping -w 0 -n 4 a-sunOS-machine' and you'll see the first test -succeed in a very short time (if you are close from the machine) and all of -the others take a much longer time (one second). With '-w 1' (wait one second -between tests, the default), everything works fine: it seems the sockets on -SunOS need time to recover :-) - -
Use all of them with care, the result is not obvious to interpret. - -
And don't forget to read RFC 1470 ("Tools for Monitoring and Debugging -TCP/IP Internets and Interconnected Devices"), specially its "Benchmark" -section and the Richard Stevens' books (all of them), published by -Addison-Wesley. diff --git a/Web/index.wml b/Web/index.wml deleted file mode 100644 index c825e0e..0000000 --- a/Web/index.wml +++ /dev/null @@ -1,84 +0,0 @@ -#use wml::template Title="echoping Home Page" - - - -
"echoping" is a small program to test (approximatively) performances of a -remote host by sending it TCP "echo" (or other protocol) packets. - -
To install it, see the INSTALL file. Or type "make" if you're in a -hurry :-) Download, if you -wish. (Or you may prefer access the latest developments via CVS: the -module is named "SRC".) You may be interested in SourceForge's page -about echoping, with the bug reports, etc. - -
To use it, simply: - -
-% echoping machine.somewhere.org -- -
or use the options before the machine name (see the man page). - -
See the DETAILS file for various traps when benchmarking networks, -specially with this program. - -
In any case, be polite: don't bother the remote host with many repeated -requests, especially with large size. Ask for permission if you often -test hosts which aren't yours. - -
Current features: - -
Known bugs - -
Examples of output: - -
-% echoping -v -s 1000 mycisco -This is echoping, version 2.0. -Trying to connect to internet address 10.99.64.1 to transmit 256 bytes... -Connected... -Sent (1000 bytes)... -Checked -Elapsed time: 0.059597 seconds -- -
-% echoping -n 10 mymachine -[...] -Minimum time: 0.170719 seconds (1500 bytes per sec.) -Maximum time: 0.211176 seconds (1212 bytes per sec.) -Average time: 0.184577 seconds (1387 bytes per sec.) -Median time: 0.181332 seconds (1412 bytes per sec.) -- -
-% echoping -h / mywww -Elapsed time: 0.686792 seconds -- -
The exit status is set if there is any problem, so you can use echoping -to test repeatedly a Web server, to be sure it runs fine. Or you can -display statistics like at Internatif. - -
To do for a future version: - -
<bortz@users.sourceforge.net>.