The two files read by the MSNL master are the configuration file and the rarp table. Their formats are described below. In both files, any line beginning with # is regarded as a comment. In the rarp table any line with a # in it is considered valid only for the part of the line proceeding the #.
This file describes the entities which the master is managing. Currently only one entity may be configured for a single master. The following example documents the file format:
# msnl.conf for sirius generated on Thu Mar 10 10:22:48 GMT 1994 # # The entity being configured. # Format of line is # primary <msnladdress> <MSNLname> <number of pods> # primary 128.232.65.42 sirius-p.cl.cam.ac.uk 1 # # Devices (pods) attached to the entity # Format of lines is # pod <number> <name> <msnladdress> <class> <type> <hwaddress> # pod 0 ln0 128.232.65.42 1 2 read-by-ioctl pod 1 yes0 128.232.129.42 5 7 none# # # Routing information for each of the pods # Format of lines is # route <name> <net>-<mask>[,....] # route ln0 0.0.0.0-0.0.0.0 route yes0 128.232.128.0-255.255.240.0
This file contains rarp response information, for two kinds of rarp requests, namely ETHER rarps and FSN (SERIAL) rarps. Each entry takes 1 line of the file. The fields are documented in the example which follows.
# # $Id: rarptable,v 1.1 1993/11/22 14:51:06 rjb17 Exp rjb17 $ # # 68k systems # # type ethernet address msnl address booter address # more comment ETHER 08:00:3e:20:49:03 128.232.68.20 # lamprey ETHER 08:00:3e:20:45:a2 128.232.68.21 # lumpfish # # FPC3 switches # # type FSN id msnl address booter address # more comment SERIAL 34 128.232.133.131 128.232.65.27 # king03 SERIAL 55 128.232.133.83 128.232.65.27 # duke03