[HECnet] Is MIM running?

[Robert Armstrong]

>  "dnping" in Linux?  

  There is a dnping in Linux DECnet.  


bob at ziti:~$ dnping legato
Sent 10 packets, Received 10 packets
bob at ziti:~$ dnping -v legato
PKT: 1      WRITE: 40 READ: 40
PKT: 2      WRITE: 40 READ: 40
PKT: 3      WRITE: 40 READ: 40
PKT: 4      WRITE: 40 READ: 40
PKT: 5      WRITE: 40 READ: 40
PKT: 6      WRITE: 40 READ: 40
PKT: 7      WRITE: 40 READ: 40
PKT: 8      WRITE: 40 READ: 40
PKT: 9      WRITE: 40 READ: 40
PKT: 10     WRITE: 40 READ: 40
Sent 10 packets, Received 10 packets

bob at ziti:~$ dnping
Usage:

dnping nodename [user pass] count

        *or*

dnping [options] nodename
        where [options]:
        -c number      number of packets to send {10}
        -d             debug mode {OFF}
        -i interval    interval between packets in microseconds {0}
        -p password    access control password {}
        -q             quiet mode {OFF}
        -s size        size of frame to send in bytes {40 data + 68 hdr}
        -t             timestamps mode {OFF}
        -u username    access control username {}
        -v             verbose mode {OFF}
        -w seconds     maximum wait time (timeout)


bob at ziti:~$ man dnping
DNPING(1)                   General Commands Manual
DNPING(1)

NAME
       dnping - Loopbacks diagnostic packets through a remote node

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

DESCRIPTION
       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.

OPTIONS
       -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)

EXAMPLES
       Pings 10 packets through remote node "mv3100"

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

           # dnping  -vti 1000000 marsha

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