Home | History | Annotate | Line # | Download | only in bootpd
Problems revision 1.1 
      1  1.1  gwr 
      2  1.1  gwr Common problems and ways to work around them:
      3  1.1  gwr 
      4  1.1  gwr Bootpd complains that it "can not get IP addr for HOSTNAME"
      5  1.1  gwr 
      6  1.1  gwr 	If the entry is a "dummy" (not a real host) used only for
      7  1.1  gwr 	reference by other entries, put '.' in front of the name.
      8  1.1  gwr 
      9  1.1  gwr 	If the entry is for a real client and the IP address for
     10  1.1  gwr 	the client can not be found using gethostbyname(), specify
     11  1.1  gwr 	the IP address for the client using numeric form.
     12  1.1  gwr 
     13  1.1  gwr Bootpd takes a long time to finish parsing the bootptab file:
     14  1.1  gwr 
     15  1.1  gwr 	Excessive startup time is usually caused by waiting for
     16  1.1  gwr 	timeouts on failed DNS lookup operations.  If this is the
     17  1.1  gwr 	problem, find the client names for which DNS lookup fails
     18  1.1  gwr 	and change the bootptab to specify the IP addresses for
     19  1.1  gwr 	those clients using numeric form.
     20  1.1  gwr 
     21  1.1  gwr 	When bootptab entries do not specify an ip address, bootpd
     22  1.1  gwr 	attempts to lookup the tagname as a host name to find the
     23  1.1  gwr 	IP address.  To suppress this default action, either make
     24  1.1  gwr 	the entry a "dummy" or specify its IP numeric address.
     25  1.1  gwr 
     26  1.1  gwr 	If your DNS lookups work but are just slow, consider either
     27  1.1  gwr 	running bootpd on the same machine as the DNS server or
     28  1.1  gwr 	running a caching DNS server on the host running bootpd.
     29  1.1  gwr 
     30  1.1  gwr My huge bootptab file causes startup time to be so long that clients
     31  1.1  gwr give up waiting for a reply.
     32  1.1  gwr 
     33  1.1  gwr 	Truly huge bootptab files make "inetd" mode impractical.
     34  1.1  gwr 	Start bootpd in "standalone" mode when the server boots.
     35  1.1  gwr 
     36  1.1  gwr 	Another possibility is to run one bootpd on each network
     37  1.1  gwr 	segment so each one can have a smaller bootptab.  Only one
     38  1.1  gwr 	instance of bootpd may run on one server, so you would need
     39  1.1  gwr 	to use a different server for each network segment.
     40  1.1  gwr 
     41  1.1  gwr My bootp clients are given responses with a boot file name that is
     42  1.1  gwr not a fully specified path.
     43  1.1  gwr 
     44  1.1  gwr 	Make sure the TFTP directory or home directory tags are set:
     45  1.1  gwr 	:td=/tftpboot:	(or)
     46  1.1  gwr 	:hd=/usr/boot:	(for example)
     47  1.1  gwr 
     48