bootpd.1m (2010 09)

b
bootpd(1M) bootpd(1M)
else continue the search
Tags for client entries
ba This tag specifies that bootpd
should broadcast the boot reply to the client. As a boolean tag,
it causes
bootpd to send the boot reply on the configured broadcast address of each network
interface. You can also assign the tag an IP-address value, which specifies the specific IP or
broadcast address for the boot reply.
bf=filename
This tag specifies the filename of the bootfile that the client should download. The client’s boot
request, and the values of the
hd (see below) and
bf symbols, determine the contents of the
bootfile field in the boot reply packet.
If the client specifies an absolute path name (in its boot request), and that file is accessible on
the server machine (see below),
bootpd returns that path name in the reply packet. If the
file is not accessible, the request is discarded; no reply is sent. If the client specifies a relative
path name, bootpd constructs a full path name by appending the relative path name to the
value of the hd tag, and tests to determine if the full path name is accessible. If the full path
name is accessible, it is returned in the boot reply packet; if not, the request is discarded.
Clients that do not specify boot files in their boot requests always elicit a reply from the server.
The exact reply depends on the values of the
hd and bf tags. If the bf tag specifies an abso-
lute path name, and the file is accessible, that path name is returned in the reply packet. Oth-
erwise, if the hd and bf tags together specify an accessible file, that file name is returned in
the reply. If a complete file name cannot be determined, or the file is not accessible publicly,
the reply contains a zeroed-out bootfile field.
If the
tftp pseudo-user exists, bootpd treats all path names (absolute or relative) as being
relative to the home directory of tftp and checks there first. If the file is not accessible under
the tftp home directory or the tftp pseudo-user does not exist, bootpd checks for the file
relative to /.
For a file to be available, it must exist, and be publicly readable.
All file names are first tried as filename
.hostname and then simply as filename . However, in
the case when the
tftp pseudo-user exists, but filename .hostname and filename are not
accessible under the tftp home directly, only filename is checked relative to /.
Note that a file considered to be accessible relative to
/ might not actually be accessible via
tftp if the command line arguments to tftpd disallow that path.
bs=size
This tag specifies the size of the bootfile. The parameter size can be either a decimal, octal, or
hexadecimal integer specifying the size of the bootfile in 512-octet blocks, or the keyword
auto, which causes the server to automatically calculate the bootfile size at each request.
Specifying the bs symbol as a boolean has the same effect as specifying auto
as its value.
ci=client_ID
This tag specifies the client identifier of the client. The parameter client_ID can be either a
hexadecimal integer, or a string contained in double quotes. The client_ID is a unique
identifier that the DHCP client may use to identify itself to the server. If present, the client
identifier supersedes the hardware address, so a client and an entry will only match in one of
two situations: one, they both have the same client identifier, or two they both have the same
hardware address and neither has a client identifier. If a request has a client identifier, then
that is used to match the client up with an entry in the bootp configuration file. One common
client ID used is to concatenate the hardware type (e.g. 0x01 for ethernet) with the hardware
address.
cs=ip_address_list
This tag specifies the IP addresses of RFC865 Quote of the Day (cookie) servers.
dn=domain_name
This tag specifies the domain name of the client for Domain Name Server resolution (see
RFC1034).
ds=ip_address_list
This tag specifies the IP addresses of RFC1034 Domain Name servers.
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010