mirror of
https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git
synced 2024-11-15 23:05:49 +01:00
48 lines
1.8 KiB
Plaintext
48 lines
1.8 KiB
Plaintext
|
|
||
|
|
Common problems and ways to work around them:
|
||
|
|
|
||
|
|
Bootpd complains that it "can not get IP addr for HOSTNAME"
|
||
|
|
|
||
|
|
If the entry is a "dummy" (not a real host) used only for
|
||
|
|
reference by other entries, put '.' in front of the name.
|
||
|
|
|
||
|
|
If the entry is for a real client and the IP address for
|
||
|
|
the client can not be found using gethostbyname(), specify
|
||
|
|
the IP address for the client using numeric form.
|
||
|
|
|
||
|
|
Bootpd takes a long time to finish parsing the bootptab file:
|
||
|
|
|
||
|
|
Excessive startup time is usually caused by waiting for
|
||
|
|
timeouts on failed DNS lookup operations. If this is the
|
||
|
|
problem, find the client names for which DNS lookup fails
|
||
|
|
and change the bootptab to specify the IP addresses for
|
||
|
|
those clients using numeric form.
|
||
|
|
|
||
|
|
When bootptab entries do not specify an ip address, bootpd
|
||
|
|
attempts to lookup the tagname as a host name to find the
|
||
|
|
IP address. To suppress this default action, either make
|
||
|
|
the entry a "dummy" or specify its IP numeric address.
|
||
|
|
|
||
|
|
If your DNS lookups work but are just slow, consider either
|
||
|
|
running bootpd on the same machine as the DNS server or
|
||
|
|
running a caching DNS server on the host running bootpd.
|
||
|
|
|
||
|
|
My huge bootptab file causes startup time to be so long that clients
|
||
|
|
give up waiting for a reply.
|
||
|
|
|
||
|
|
Truly huge bootptab files make "inetd" mode impractical.
|
||
|
|
Start bootpd in "standalone" mode when the server boots.
|
||
|
|
|
||
|
|
Another possibility is to run one bootpd on each network
|
||
|
|
segment so each one can have a smaller bootptab. Only one
|
||
|
|
instance of bootpd may run on one server, so you would need
|
||
|
|
to use a different server for each network segment.
|
||
|
|
|
||
|
|
My bootp clients are given responses with a boot file name that is
|
||
|
|
not a fully specified path.
|
||
|
|
|
||
|
|
Make sure the TFTP directory or home directory tags are set:
|
||
|
|
:td=/tftpboot: (or)
|
||
|
|
:hd=/usr/boot: (for example)
|
||
|
|
|