multinet - Connect to a Multinet* DECnet over IP server
[options] <local-decnet-addr> <remote-host>
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.
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.
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
- http://www.process.com and is available free for hobbyist
The protocol used here was reverse engineered by Mark Berryman and Christine
- Be verbose and dump packet contents to stderr
- Advertise as a level 1 router
- Advertise as a level 2 router (default)
- Make the tapX device into the default DECnet device. This
will force all traffic to non-local nodes down the Multinet link.
IMPORTANT: 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
- -H hello timer
- How often HELLO messages are sent (default 60) in seconds.
multinet -1 -D 3.2 zarqon.tykepenguin.com