Q: I am a software engineering co-op, and networks is certainly not one of my stronger points. I must ficure how to establish the dhcpsvc.conf, dhcptab, and what other files I need.
Re:I know DHCP is intended to be dynamic. Right now we have a hacked version of bootp doing the job, but my boss wants it replaced with a standard implementation.
Re:This is what you do:
ACtually, I was going to type it out, but luckily I found something good on google..:D
<—-Lazy bastard:D
At any rate, to change from DHCP to static, you will need to erase the /etc/dhcp.hme0 file and create an /etc/hostname.hme0 file. The /etc/hostname.hme0 should have the logical name you wish to assign to the host. You should then create a corresponding IP/hostname binding in /etc/hosts so that the OS will know how to bind the interface at reboot.
You will also need to set the hostname with `hostname YourMachinesName`, then run `hostname > /etc/nodename`.
You will likely need to set a default route. Create the file /etc/defaultrouter with the IP address of the router.
Re:sorry. I only know how to set it up on linux.
Concering netowrking, what you are asking is different from DHCP. DHCP stand for Dynamic Host Configuration Protocol. Since you want STATIC IPs instead of Dynamically assigned ones, you must set each PCs IP at the machines themselves.
Then the gateway address should point to the main server or whatever.
For example, once you figure it out, here is a fictional setup
The gateway server will be IP 10.10.10.1
The clients will follow the Pattern, 10.10.10.x, replacing the x with a unique number.
The clients will use the address 10.10.10.1 as their gateway IP which connects them to the WEB or another netowrk.
Re:guy, I've seen the Sun documentation for it. I guess I need my boss to figure out how he wants the DHCP options set up. Do you know how to set it up so that a piece of equipment always has the same IP? I have about 60 pieces of equipment in a lab that need to have the same IP address forever.
Re:The dhcpsvc.conf file resides in directory /etc/inet and
contains parameters for specifying Dynamic Host Configura-
tion Protocol (DHCP) service configuration settings, includ-
ing the type and location of DHCP data store used.
The description of the dhcpsvc.conf file in this man page is
informational only. The preferred method of setting or modi-
fying values within the dhcpsvc.conf file is by using
dhcpconfig(1M) or the dhcpmgr(1M) utility. Do not edit the
dhcpsvc.conf file.
The dhcpsvc.conf file format is ASCII; comment lines begin
with the crosshatch (#) character. Parameters consist of a
keyword followed by an equals (=) sign followed by the
parameter value, of the form:
Keyword=Value
The following Keyword and Value parameters are supported:
BOOTP_COMPAT
String. automatic or manual. Enables support of BOOTP
clients. Default is no BOOTP. Value selects BOOTP
address allocation method. automatic to support all
BOOTP clients, manual to support only registered BOOTP
clients. server mode only parameter.
CACHE_TIMEOUT
Integer. Number of seconds the server will cache data
from data store. Used to improve performance. Default
is 10 seconds. server mode only parameter.
CONVER
Integer. Container version. Used by DHCP administra-
tive tools to identify which version of the public
module is being used to administer the data store.
CONVER should not be changed manually.
DAEMON_ENABLED
TRUE/FALSE. If TRUE, the DHCP daemon can be run. If
FALSE, DHCP daemon process will exit immediately if
the daemon is started. Default is TRUE. Generic param-
eter.
HOSTS_DOMAIN
String. Defines name service domain that DHCP adminis-
tration tools use when managing the hosts table. Valid
SunOS 5.9 Last change: 3 Oct 2001 1
File Formats dhcpsvc.conf(4)
only when HOSTS_RESOURCE is set to nisplus or dns.
HOSTS_RESOURCE
String. Defines what name service resource should be
used by the DHCP administration tools when managing
the hosts table. Current valid values are files,
nisplus, and dns.
ICMP_VERIFY
TRUE/FALSE. Toggles ICMP echo verification of IP
addresses. Default is TRUE. server mode only parame-
ter.
INTERFACES
String. Comma-separated list of interface names to
listen to. Generic parameter.
LOGGING_FACILITY
Integer. Local facility number (0-7 inclusive) to log
DHCP events to. Default is not to log transactions.
Generic parameter.
OFFER_CACHE_TIMEOUT
Integer. Number of seconds before OFFER cache timeouts
occur. Default is 10 seconds. server mode only param-
eter.
PATH Path to DHCP data tables within the data store speci-
fied by the RESOURCE parameter. The value of the PATH
keyword is specific to the RESOURCE.
RELAY_DESTINATIONS
String. Comma-separated list of host names and/or IP
addresses of relay destinations. relay mode only
parameter.
RELAY_HOPS
Integer. Max number of BOOTP relay hops before packet
is dropped. Default is 4. Generic parameter.
RESCAN_INTERVAL
Integer. Number of minutes between automatic dhcptab
rescans. Default is not to do rescans. server mode
only parameter.
RESOURCE
Data store resource used. Use this parameter to name
the public module. See the PATH keyword in
dhcp_modules(5).
RESOURCE_CONFIG
String. This might be used for a database account name
SunOS 5.9 Last change: 3 Oct 2001 2
File Formats dhcpsvc.conf(4)
or other authentication or authorization parameters
required by a particular data store. dhcp_modules(5).
Providers can use the RESOURCE_CONFIG known as config-
ure by specifying an optional service provider layer
API function:
int configure(const char *configp);
If this function is defined by the public module pro-
vider, it is called during module load time by the
private layer, with the contents of the
RESOURCE_CONFIG string acquired by the administrative
interface (in the case of the dhcpmgr, through the use
of a public module-specific java bean extending the
dhcpmgr to provide a configuration dialog for this
information.
RUN_MODE
server or relay. Selects daemon run mode. Default is
server.
SECONDARY_SERVER_TIMEOUT
Integer. The number of seconds a secondary server will
wait for a primary server to respond
before responding itself. Default is 20 seconds. This
is a server
mode only parameter.
UPDATE_TIMEOUT
Integer. Number of minutes to wait for a response from
the DNS server before timing out. If this parameter is
present, the DHCP daemon will update DNS on behalf of
DHCP clients, and will wait the number of seconds
specified for a response before timing out. You can
use UPDATE_TIMEOUT without specifying a number to
enable DNS updates with the default timeout of 15
seconds. If this parameter is not present, the DHCP
daemon will not update DNS for DHCP clients.
VERBOSE
TRUE/FALSE. Toggles verbose mode, determining amount
of status and error messages reported by the daemon.
Default is FALSE. Set to TRUE only for debugging. Gen-
eric parameter.
0 Comments.