Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

multinet(8) [debian man page]

MULTINET(8)						      System Manager's Manual						       MULTINET(8)

NAME
multinet - Connect to a Multinet* DECnet over IP server SYNOPSIS
multinet [options] <local-decnet-addr> <remote-host> DESCRIPTION
This utility creates a tapX device and copies all the DECnet packets from that over IP to a remote Multinet* server. It provides a way to connect a Linux box to a remote VMS machine over an IP-only network. Using Linux routing it should be possible to connect DECnet networks over the internet using this technique. local-decnet-addr DECnet node address of the tapX interface. This need not be the same as the address used on other interfaces but it might be less confusing if it is. remote-host IP address or host name of the remote Multinet server. If you send a HUP signal to the process it will lookup this name again, so you don't need to restart the server if the remote node changes its IP address. *Multinet is a product, and probably a trademark, of Process Software. http://www.process.com and is available free for hobbyist use. The protocol used here was reverse engineered by Mark Berryman and Christine Caulfield. OPTIONS
-v Be verbose and dump packet contents to stderr -1 Advertise as a level 1 router -2 Advertise as a level 2 router (default) -D Make the tapX device into the default DECnet device. This will force all traffic to non-local nodes down the Multinet link. IMPOR- TANT: Due to a kernel bug you should not use this option unless you are using a Linux kernel version 2.6.17 or later. -p priority Router priority. Default is 64 -P port Port to talk to Multinet on (default is 700). Ony change this if you know the Multinet server is listening on a different port -m MTU Maximum size of packets. (default 576) -t secs Timeout for IP connections. If no traffic is seen on the IP connection after this time then the daemon will attempt to restart it. -H hello timer How often HELLO messages are sent (default 60) in seconds. EXAMPLES
multinet -1 -D 3.2 zarqon.tykepenguin.com SEE ALSO
dnroute(8), ip(8) DECnet utilities March 30 2006 MULTINET(8)

Check Out this Related Man Page

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 for- ever. -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) DECnet utilities January 25 2000 DNPING(1)
Man Page