Technical article 111069

How to configure a UnixWare7 or OpenServer6 server as a DHCP client.

OpenServer 6.0.0UnixWare 7.1.0UnixWare 7.1.1UnixWare 7.1.2UnixWare 7.1.3UnixWare 7.1.4Open UNIX 8

Written · Last revised

Problem

How do I configure my UnixWare7 or OpenServer6 server as a DHCP client?

Solution

Configuring a system as a DHCP client allows it to obtain its basic
TCP/IP configuration parameters (domain name, IP address, netmask,
broadcast address, default router, and DNS parameters) from a DHCP
server at boot time.  You must have a DHCP server configured prior
to configuring a client.

To configure your server as a DHCP client, you must do these two things, which are detailed below:

- Configure the TCP/IP on your Network Interface Card (NIC) to be a DHCP client.

- Create a dhcpc.conf file.

Doing these two things will alter the file /etc/inet/config to start dhcpc, the DHCP Client Daemon, on system startup.

First you must configure TCP/IP. When you tell the machine that it is a DHCP client, it ignores any domain name, IP address, netmask, and broadcast address you may have previously configured.

To configure TCP/IP:
1. Run "netcfg" as root.

2. Click on "TCP/IP" under the network card you want to configure (you can only configure one per machine).

3. Click on "Protocol -> Modify Protocol Configuration..."

4. Then click on "Yes" for "DHCP client". You will notice that previously configured parameters are stippled out.

After you perform the above steps, you must create or modify the file:

/etc/inet/dhcpc.conf

to let dhcpc, the DHCP daemon, know what options to use. A very simple file is attached below. For more specifics on what options you need, consult the person administrating your DHCP server. For more information, see man dhcpc(1Mtcp) and man dhcpc.conf(4tcp).

##-------SAMPLE dhcpc.conf configuration file----------
# DHCP client configuration file
#
# fields separated by ':' are
#       <Keyword>:<Parameters>
#
# recognised keywords are:
#       debug(0-10, def 1), gratuitous(0|1, def 1), command_timeout(secs),
#       dynamic_dns(0|1, def 0)
#       request_address(ipaddr), param_req(list string)
#       select_timeout(secs), lease_time(secs),
#       user_id(string), vendor_id(string),
#       max_message_size(int)
#
# multiple param_req definitions per line are allowed.
#
# vendor:vendor_id:opt:type:keyword
# command:run:path:options
#
# commands are executed in order listed below
#
#
## Requested Options
param_req:subnet_mask domain_name broadcast_address dns_servers
param_req:time_offset routers hostname
## Sample Vendor options
## Your DHCP server administrator will supply you with these
vendor_id:sco_opts
vendor:sco_opts:1:STRING:DNS_SEARCH
## Commands
command:y:/etc/inet/dhcpc/opt:
command:y:/etc/inet/dhcpc/info:
## Dynamic DNS update, run dynamic command last
#dynamic_dns:1
#command:y:/etc/inet/dhcpc/dynamic:-t 3600

See also

Manual pages: dhcpc(1Mtcp), dhcpc.conf(4tcp), dhcpd(1Mtcp),
dhcpd.conf(4tcp)

ta110134, "Configuring a Windows 95 PC as a DHCP client to UnixWare 7."

The UnixWare 7 online documentation via the UnixWare Desktop or via scohelp or http://uw7doc.sco.com and search on "dhcp".

ta111070, "How to use UnixWare 7 with DSL Internet access."

From the Xinuos technical article database, record 111069. Reproduced with permission. The original is at www.sco.com/ta/111069, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.