client.pcy - BOOTP and DHCP client policy
The client.pcy file is a text database, read by the joinc daemon on startup, which governs the behavior of BOOTP and DHCP clients. If the JOINCONFIG variable is present in the joinc environment, it is taken to be the directory where client.pcy is housed; otherwise joinc searches the /etc/join directory. Defaults exist for all parameters and switches, so it is not an error if the file does not exist.
Blank lines are ignored. The number sign (#) introduces a comment which continues to the next newline. Each new policy option must begin and end on a separate line. Policy options are introduced by a keyword, and may be Boolean, or may take a value separated from the keyword by whitespace (but not a newline). If an option is present more than once, only the value attached to the last occurrence takes effect - earlier value(s) are forgotten.
If no DHCP responses are heard and this flag is set,
the client uses any BOOTP response in the configuration.
In this scenario, the client does not renew, rebind,
expire, or release its IP address lease. In other words the client
is given what is effectively an infinite lease.
Although the client accepts BOOTP responses,
it only sends DHCP packets. There is no guarantee
that BOOTP servers which hear these packets will
respond, since they may become confused by the
presence of DHCP data within the packet.
When the client receives an IP address from the server, it
performs an ARP on the local network to verify that
no other client is using the address. If the client receives no reply after
seconds expires, it assumes that it may use the address.
Default: 2 seconds. The client's class ID. Consult RFC1541 for details. Use a client identifier other than the MAC address. Currently setting client_id tells the DHCP client daemon to use a concatenation of the MAC address and the interface name as the client ID. The MAC address is in internal form, not the readable, colon-separated string. You must use this option when configuring a client with multiple interfaces and where the client's MAC address is the same on each interface (SUN hardware for example). The DHCP server grants the client permission to use an IP address for a fixed period of time (which may be infinite). In the language of DHCP, the client is granted a "lease" on the IP address. With this parameter, the client may request a lease of a particular duration, although servers are not bound to honor the request. If the client does not care, seconds should be set to zero; if an infinite lease is required, to minus one, -1. Otherwise specify in seconds the lease duration required.
Default: 0 This parameter is subtly different from the number of retries a client will make as part of an exponential broadcast retry backoff. Rather it is the number of separate attempts the client will make to contact a server, assuming that replies are received, but that the client, for one reason or another, rejected those replies.
Default: 2 Clients are required by the DHCP protocol to implement an exponential retransmission and backoff when broadcasting discover or request packets. The array of values specifies how long the client should wait for replies before timing out and retrying the broadcast.