DESCRIPTION
===========

This is a partially completed port of the Linux DHCP Client program dhcpcd-0.70
to OpenVMS systems running Multinet.



REQUIREMENTS
============

To compile and run this version of DHCPC, you need Multinet.  DHCPC has been
known to compile with DEC C 5.6 and run under Multinet 4.0B and OpenVMS 7.1.



BUILDING
========

Just type

   $ @MAKE

It's that simple!



INSTALLATION
============

0) You should configure Multinet so that it starts up with IP address
   0.0.0.0.  Consult your Multinet Administrator's Guide for more information.

1) Edit DHCPC.COM and examine the line which reads

   $  Mcr DHCPC_DIR:DHCPC.EXE   se0   EWA0

   If your Multinet network interface is not se0, replace it with the correct
   interface name.  If the VMS_DEVICE associated with the interface is not
   EWA0, replace it with the correct VMS device name.  Consult your Multinet
   Administrator's Guide for more information.

2) Edit DHCPC-STARTUP.COM and in the line where it says

   $ Define /System /Executive /noLog   DHCPC_DIR   disk:[directory]

   replace "disk:[directory]" with the location where you plan to keep
   DHCPC.COM, DHCPC.EXE, and FORCEX.EXE.

3) Copy DHCPC.COM and DHCPC.EXE and FORCEX.EXE to the DHCPC_DIR directory that
   you indicated in the previous step.

4) Edit SYS$STARTUP:SYSTARTUP_VMS.COM and add the following line somewhere
   AFTER the Multinet startup commands:

   $ @SYS$STARTUP:DHCPC-STARTUP.COM

5) Edit SYS$STARTUP:SYSHUTDWN.COM and add the following line:

   $ @SYS$STARTUP:DHCPC-SHUTDOWN.COM

6) Copy DHCPC-STARTUP.COM and DHCPC-SHUTDOWN.COM to the SYS$STARTUP directory.



KNOW PROBLEMS
=============

*  When the assigned IP address changes at the renewal time, the system
   does not always handle the change very gracefully.  On rare occasions you
   may need to restart the MULTINET_SERVER process.  Consult the Multinet
   documentation for details on how to do this.

*  This port was derived from a version of dhcpcd which was optimized for
   usage with Time Warner Road Runner cable modem DHCP servers.  You may need
   to tinker with the program a bit to get it to work well in other
   environments.

*  You must manually configure your DNS, NTP, SMTP, POP, and other options.
   If the DHCP server gives information regarding these options, they should
   appear under the DHCPC_DIR directory in the files named *.conf.  Currently
   you must read these files, and, if needed, manually (re)configure Multinet
   and restart MULTINET_SERVER.  Consult your Multinet documentation for
   details on how to do this.

   For example, DNS information is contained in DHCPC_DIR:RESOLV.CONF.  The
   file might look like this:

domain hawaii.rr.com
nameserver 24.25.227.32
nameserver 24.25.227.34
nameserver 24.25.227.36

   If these values are different from before, you should edit the file
   MULTINET:DOMAIN-NAME-SERVICE.CONFIGURATION and change the "forwarders"
   entry to:

forwarders   24.25.227.32   24.25.227.34   24.25.227.36

   and restart the MULTINET_SERVER process:

$ @MULTINET:START_SERVER



Everett Chong
echong@my-deja.com
