Provided by: dnet-progs_2.65build2_amd64 bug


       dnping - Loopbacks diagnostic packets through a remote node


       dnping nodename [user pass] count
       dnping nodename [options] nodename
       [qsv] [-c number] [-i interval] [-p password] [-s size] [-u username] [-w timeout]


       This utility sends to remote DECnet node nodename the number of packets specified by count
       to test the link between the two systems.  Optionally  a  username  and  password  may  be
       specified  for  the  connection  as well as several other options. NOTE that if you dnping
       another Linux box it must have dnetd running.
       NOTE also that dnping is not really like an IP "ping" in that it needs a registered object
       at  the  other  end  to  connect  to. So, just because you cannot ping a machine does not,
       necessarily, mean that machine is not available,  just  that  the  MIRROR  object  is  not
       available.  There  is  not  (to my knowledge) a low-level equivalent in DECnet of the ICMP
       ping message.


       -c number
              Number of packets to send (default 10)

       -d     Debug mode (default off)

       -i interval
              interval between packets in microseconds (default 0)

       -p password
              Access control password. If this is "-" then you will be prompted.

       -q     Quiet mode (default off)

       -s size
              size of frame to send in bytes (40 data + 68 hdr)

       -t     timestamps mode (default off)

       -u username
              access control username

       -w timeout
              Specifies a timeout (in seconds). If not response is received after this time  then
              dnping will abort. The default is to wait forever.

       -v     verbose mode (default off)


       Pings 10 packets through remote node "mv3100"

           # dnping mv3100 10
       Make it look a bit like IP ping:

           # dnping  -vti 1000000 marsha


       dntype(1), dndir(1), dndel(1), dntask(1), sethost(1), dnetd(8)