HP-UX Reference (11i v2 07/12) - 1M System Administration Commands A-M (vol 3)
b
bootpd(1M) bootpd(1M)
client relay entry from a group relay entry. The linear sorted table is sorted on the value of tag
hm. The
search and match mechanism is explained in the discussion of tag
hm.
Tags for both kinds of entries
ha=hardware-address
This tag specifies the hardware address of the client. The hardware address must be specified in
hexadecimal; optional periods and/or a leading
0x can be included for readability. The ha tag
must be preceded by the
ht tag (either explicitly or implicitly; see
tc below).
ht=hardware-type
This tag specifies the hardware type code. hardware-type can be an unsigned decimal, octal, or
hexadecimal integer corresponding to one of the ARP Hardware Type codes specified in
RFC1010. It can also be specified by the symbolic names
ethernet or ether for 10-Mb Eth-
ernet;
ethernet3 or ether3 for 3-Mb experimental Ethernet;
ieee802, tr,ortoken-
ring
for IEEE 802 networks; pronet for Proteon ProNET Token Ring;
chaos, and arcnet,
for Chaos and ARCNET, respectively.
tc=template-host
This tag indicates a table continuation. Often, many host entries share common values for cer-
tain tags (such as domain servers, etc.). Rather than repeatedly specifying these tags, a full
specification can be listed for one host entry and shared by others via the tc
mechanism.
The template-host is a dummy host that does not actually exist and never sends boot requests.
Information explicitly specified for a host always overrides information implied by a
tc tag sym-
bol. The value of template-host can be the host name or IP address of any host entry previously
listed in the configuration file.
Sometimes it is necessary to delete a specific tag after it has been inferred via
tc. This can be
done using the construction tag@ which removes the effect of tag. For example, to completely
undo an RFC1034 domain name server specification, use
:ds@: at an appropriate place in the
configuration entry. After removal with @, a tag is eligible to be set again through the
tc
mechanism.
Tags for relay entries
bp=bootp-servers
This tag specifies the BOOTP servers that DHCP/BOOTP requests will be relayed to. The value
of bootp-servers can be one or more individual IP addresses, and/or one or more network broad-
cast addresses. A relay entry with this tag configured indicates that the relay function is on for
the clients specified in this entry. A relay entry missing this symbol means that the relay func-
tion is off for the clients specified in this entry.
th=threshold
This tag specifies the threshold value in seconds for the entry. The default value is 0.
hp=hops
This tag specifies the maximum hops value. If the hops value exceeds 16, it is set to 16. The
default value is 4.
hm=hardware-address-mask
This tag specifies the mask for the hardware address ha. hardware-address-mask must be
specified in hexadecimal. An optional leading
0x can be included for readability. The hm tag
must be preceded by the ht tag (either explicitly or implicitly; see tc above). Each 0 bit in hm
specifies that the corresponding bit in ha is a "don’t-care" bit, each
1 bit in hm specifies that the
corresponding bit in the
ha value is ANDed with the hm value. If the result is the same and also
the hardware type matches, then a match is found. For example,
if (((hm & ha)==(client_hw_addr & hm))
&& (ht == client_hw_type))
then a match is found
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.
106 Hewlett-Packard Company − 3 − HP-UX 11i Version 2: December 2007 Update