RARPD 1.15

To run the NT RARP daemon you need 3 files in the same directory:
- rarpd.exe
- rarp.sys
- rarpd.tbl

The first two are packaged with this file; the third is your
responsibility.  RARPD.TBL is a series of ASCII text lines, each
supplying a hex MAC address and its corresponding IP address rendered
in the convential way, e.g:

00.a0.24.19.ae.d4 192.168.0.1

There is no need to do anything once you have updated the file while
RARPD is running; the program will notice that the file has been changed
the next time a RARP request comes in.

There is one possible optional argument, which can be useful with a
multi-homed server.  If you have such a machine and a card you want to
*exclude* (not use) is e.g. on the 140.251.211.* network, you'll want
to add "/XS140.251.211.0 to the command line.  You can use the
"/XS..." argument multiple times to exclude multiple networks.
Remember, you code the *network*, not the full IP address.

At present we parse this very strictly and simply, so don't put any
extra whitespace in.  That's all!

TROUBLE?

If at all possible, a bug report should include the file rarpd.log,
which is written into the directory rarpd is run from.

Also in this package is a program called regdump which was useful in
figuring out details of the Registry not reported by Microsoft's
regedit.  It is entirely passive, i.e. it looks but does not touch.
Please don't lose it; if you find that rarpd doesn't work for you
and contact the author you will probably be asked to run regdump to
gather diagnostic information.

If you experience trouble with rarpd and want to be helpful without
exerting a lot of effort, just run ipregdmp.bat, which is included in
this archive.  It will emit a file called ipregdmp.log, containing the
registry info most likely to pertain to the problem; emailing that
file to the author should do it.

One last word on sending me logfiles: Please don't encode them, as
they're all straight ASCII.
