ATPING(1M) K-Talk by Xinet (05/12/00 10.2) ATPING(1M)
NAME
atping - ping an AppleTalk node
SYNOPSIS
atping [-l len] [-x] [-b] [-c] net.node
atping-O name [-T type ] [-Z zone ] [-x] [-b] [-c] [-t] [-l
DESCRIPTION
The atping command attempts to use the Apple Echo Protocol
(AEP) to ping an AppleTalk node. It is similar in function
to ping(1m). In its usual usage, atping is given an
AppleTalk net and node number, and it sends an echo request
every second. It waits for response packets, and lists each
one as it is received. The output includes a round trip
time, and a count of packets received and lost. The net and
node arguments can be prepended with a 0x to specify
hexadecimal input.
-x causes atping to print its output in
hexadecimal.
-b (blast) flag causes atping to send packets as
quickly as possible to test the load-handling
of another machine. A count of the number of
packets sent and received is kept. The high
packet volume produced may crash some routers.
-c (compare) flag causes atping to compare the
return packets to ensure the packets are not
getting corrupted in transit. Can be used in
conjunction with -b
-l flag makes the echo packets len bytes long.
The default is 586, which is also the maximum.
-t makes atping wait at most 1 second for a
response, and exit with a code indicating
success (0) or failure (errno). This is good
for detecting in a script if a machine has
failed.
-O, -T, and -Z
options cause atping to use NBP to look up the
address of the entity. If the entity you wish
to ping is running K-Talk, you can simply
specify the machine's name, with the -O option.
If the entity you wish to ping is another
device (such as a printer), you can specify the
type with -T (which defaults to "Echoer") and
the zone with -Z (which defaults to "*", the
local zone). atping is usually used to check
network connectivity. If there is no route
Page 1 (printed 5/15/100)
ATPING(1M) K-Talk by Xinet (05/12/00 10.2) ATPING(1M)
available to the specified net, atping will
return "network is unreachable".
CAVEATS
When routers with multiple interfaces configured for
AppleTalk are pinged, they may return a ``from'' address
from an interface other than the one addressed. This is
normal.
Page 2 (printed 5/15/100)
