echoping/SRC/echoping.1

204 lines
6.3 KiB
Groff
Raw Normal View History

2000-06-30 06:57:29 +00:00
.\" $Id$
2000-04-13 09:19:23 +00:00
.TH echoping 1 "November 22, 1996" "ECHOPING" "echoping"
.SH NAME
echoping \- tests a remote host with TCP or UDP
.SH SYNOPSIS
.B echoping
2002-10-03 19:49:15 +00:00
.RI [-4]
.RI [-6]
2001-02-23 10:41:22 +00:00
.RI [-v]
.RI [-r]
.RI [-f fill]
.RI [-t timeout]
.RI [-c]
.RI [-d]
.RI [-u]
.RI [-s size]
.RI [-n number]
.RI [-w delay]
.RI [-h url]
.RI [-i url]
.RI [-p priority]
.RI [-P tos]
.RI [-C]
.RI [-S]
.RI [-A]
.RI [-a]
2000-04-13 09:19:23 +00:00
.B hostname
[:port]
.SH DESCRIPTION
.LP
.B echoping
is a small program to test (approximatively) performances
of a remote Internet host by sending it TCP "echo" packets. It can use other
2000-06-30 06:57:29 +00:00
protocols as well (HTTP - which makes it a good tool to test Web servers, UDP "echo", etc).
2000-04-13 09:19:23 +00:00
.LP
.B echoping
simply shows the elapsed time, including the time to set up the TCP
connection and to transfer the data. Therefore, it is unsuitable to physical
line raw throughput measures (unlike bing or treno). On the other end, the
action it performs are close from, for instance, a HTTP request and it is meaningful
to use it (carefully) to measure Web performances.
.SH ARGUMENT
.IP hostname[:port]
2002-10-11 20:17:57 +00:00
Name (or address) of the server to test. For HTTP, you can specify a
port number. For HTTP and IPv6, you can use RFC 2732 syntax (you will
probably need to escape the brackets from the shell).
2000-04-13 09:19:23 +00:00
.SH OPTIONS
.IP -v
Verbose
.IP -s\ nnn
Size of the data to send. Large values can produce strange results with
some echo servers.
.IP -n\ nnn
2002-09-25 13:00:29 +00:00
Numbers of repeated tests. With this option, you have also the
minimum, maximum, average and median time, as well as the standard
deviation. The median is the value such that half of the measures are
under it and the other half is above. When you measure highly
variables values, like it is often the case on the whole Internet,
median is better than average to avoid "extreme" values. You can check
the "value" of the average by looking at the standard deviation: very
roughly, if the standard deviation is more than the half of the
average, the average does not mean anything. (See a book about
statistics for the details: the reality is far more complicated.)
2000-04-13 09:19:23 +00:00
.IP -w\ nnn
Number of seconds to wait between two tests (default is one). On
systems which have usleep(), you can write it as a fractional number,
such as 3.14. Otherwise, use integers.
2000-04-13 09:19:23 +00:00
.IP -t\ nnn
Number of seconds to wait a reply before giving up. For TCP, this is the
maximum number of seconds for the whole connection (setup and data exchange).
.IP -u
Use UDP instead of TCP
.IP -d
Use the "discard" service instead of echo
.IP -c
Use the "chargen" service instead of echo
.IP -h\ url
Use the HTTP protocol (instead of echo) for the given URL. The URL has to
be a relative one (for instance '/' or '/pics/foobar.gif') because HTTP 1.0
servers will not understand a request for an absolute URL.
.IP -i\ url
Use the ICP protocol (instead of echo) for the given URL. The URL has to
be an absolute one. This is mostly for testing Squid Web proxy/caches.
.IP -A
Force the proxy (if you use one) to ignore the cache
.IP -a
Force the proxy (if you use one) to revalidate data with the original server
2000-11-04 13:00:23 +00:00
.IP -C
2002-10-03 19:49:15 +00:00
Use the SSL/TLS (cryptography) protocol. For HTTP tests only.
2000-09-27 05:38:29 +00:00
.IP -S
Use the SMTP protocol (instead of echo) for the given server.
2000-04-13 09:19:23 +00:00
.IP -r
Use T/TCP (if it has been compiled with it). See the INSTALL file for details.
2002-10-03 19:49:15 +00:00
.IP -4
Use only IPv4 (even if the target machine has an IPv6 address)
.IP -6
Use only IPv6 (even if the target machine has an IPv4 address)
2000-04-13 09:19:23 +00:00
.IP -f\ character
Fill the packet with this character (default is random filling)
.IP -p\ n
Send packets with the socket priority to the integer
.IR n .
The mapping of the socket priority into a network layer or a link
layer priority depends upon the network protocol and link protocol
in use. For more details see
.B SO_PRIORITY
in
2001-03-17 20:49:24 +00:00
.BR socket(7).
.IP -P\ n
Set the IP type of service octet in the transmitted packets to the
least significant eight bits of the integer
.IR n .
2001-03-17 20:49:24 +00:00
See
.BR ip(7)
or
.BR ip(4)
(depending on your Unix). /usr/include/netinet/ip.h may contain
interesting constants for setting Type Of Service.
2000-04-13 09:19:23 +00:00
.SH EXAMPLES
.IP echoping\ \-v\ foobar.example.com
2000-04-13 09:19:23 +00:00
Tests the remote machine with TCP echo (one test).
.IP echoping\ \-n\ 5\ \-w\ 10\ foobar.example.com
2000-04-13 09:19:23 +00:00
Tests the remote machine with TCP echo (five tests, every ten seconds).
.IP echoping\ \-h\ /\ foobar.example.com
2000-04-13 09:19:23 +00:00
Tests the remote Web server and asks its home page. Note you don't
indicate the whole URL.
.IP echoping\ \-h\ http://www.example.com/\ cache.example.com:3128
2000-04-13 09:19:23 +00:00
Tests the remote Web proxy-cache and asks a Web page. Note that you must
indicate the whole URL.
.IP echoping\ -u\ \-P\ 0xa0\ foobar.example.com
Sends several UDP Echo packets with an IP Precedence of 5.
.SH IP TYPE OF SERVICE OCTET
The IP packet header contains 8 bits named the "type of service octet".
The value of the octet is set with the
.B \-P
option. The effects of the octet are defined differently in RFC791
.I "Internet Protocol"
and RFC2474
.IR "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
RFC791 defines
.I Precedence
which has ascending priorities 0 through to 7, and the bits
.IR Delay ,
.IR Throughput ,
.IR Reliability ,
and
.I Cost
which indicates the application's preference for the properties of
the packet's path through the network.
.I Precedence
is in the most significant three bits of the type of service octet,
followed in decending significance order by the
.IR D ,
.IR T ,
.I R
and
.I C
bits. The least significant bit must be zero. Only one of the
.IR D ,
.IR T ,
.I R
or
.I C
bits may be set.
RFC2474 defines the Distributed Services Code Point, or
DSCP.
This acts as a selector between 64 possible behaviours that the
network can apply to the packet. The
.I DSCP
is in the most significant six bits of the type of service octet.
The remaining least significant two bits of the octet must be
zero.
The numeric arguments to
.B -p
and
.B -P
can be in decimal (such as 11), octal (such as 013) or hexadecimal
(such as 0x0b). So padding decimal arguments with leading zeros will
change the value read.
You may need to be superuser to set some
.B -p
or
.B -P
2001-03-17 20:49:24 +00:00
values (precedence on Linux, for instance).
2000-04-13 09:19:23 +00:00
.SH BUGS
See the TODO file or SourceForge bug tracking system at
<http://sourceforge.net/bugs/?group_id=4581>.
2000-04-13 09:19:23 +00:00
.SH SEE ALSO
See the README for information about other network measurements programs.
.SH AUTHOR
2000-06-30 06:57:29 +00:00
Stephane Bortzmeyer <bortz@users.sourceforge.net>