Problems revision 50476
150476Speter# $FreeBSD: head/libexec/bootpd/Problems 50476 1999-08-28 00:22:10Z peter $ 23229Spst 33229SpstCommon problems and ways to work around them: 43229Spst 513572SpstBootpd complains: "bind: Address already in use" and fails to start. 613572Spst You are already running something that has bound the 713572Spst BOOTP listening port number. Check /etc/inetd.conf or 813572Spst the equivalent for a bootp line (or in startup files). 913572Spst 103229SpstBootpd complains that it "can not get IP addr for HOSTNAME" 113229Spst 123229Spst If the entry is a "dummy" (not a real host) used only for 133229Spst reference by other entries, put '.' in front of the name. 143229Spst 153229Spst If the entry is for a real client and the IP address for 163229Spst the client can not be found using gethostbyname(), specify 173229Spst the IP address for the client using numeric form. 183229Spst 193229SpstBootpd takes a long time to finish parsing the bootptab file: 203229Spst 213229Spst Excessive startup time is usually caused by waiting for 223229Spst timeouts on failed DNS lookup operations. If this is the 233229Spst problem, find the client names for which DNS lookup fails 243229Spst and change the bootptab to specify the IP addresses for 253229Spst those clients using numeric form. 263229Spst 273229Spst When bootptab entries do not specify an ip address, bootpd 283229Spst attempts to lookup the tagname as a host name to find the 293229Spst IP address. To suppress this default action, either make 303229Spst the entry a "dummy" or specify its IP numeric address. 313229Spst 323229Spst If your DNS lookups work but are just slow, consider either 333229Spst running bootpd on the same machine as the DNS server or 343229Spst running a caching DNS server on the host running bootpd. 353229Spst 363229SpstMy huge bootptab file causes startup time to be so long that clients 373229Spstgive up waiting for a reply. 383229Spst 393229Spst Truly huge bootptab files make "inetd" mode impractical. 403229Spst Start bootpd in "standalone" mode when the server boots. 413229Spst 423229Spst Another possibility is to run one bootpd on each network 433229Spst segment so each one can have a smaller bootptab. Only one 443229Spst instance of bootpd may run on one server, so you would need 453229Spst to use a different server for each network segment. 463229Spst 473229SpstMy bootp clients are given responses with a boot file name that is 483229Spstnot a fully specified path. 493229Spst 503229Spst Make sure the TFTP directory or home directory tags are set: 513229Spst :td=/tftpboot: (or) 523229Spst :hd=/usr/boot: (for example) 533229Spst 5413572SpstMy PC clients running Sun's PC-NFS Pro v1.1 fail to receive 5513572Spstacceptable responses from the bootp server. 5613572Spst 5713572Spst These clients send a request with the DHCP "message length" 5813572Spst option and the (new) BOOTP "broadcast flag" both set. 5913572Spst The bootp server (on SunOS) will send a fragmented reply 6013572Spst unless you override the length with :ms=1024: (or less). 6113572Spst The "broadcast flag" is not yet supported, but there is 6213572Spst a simple work-around, just add :ra=255.255.255.255: 6313572Spst for any clients that need their reply broadcasted. 6413572Spst You may need to use a differnet broadcast address. 6513572Spst (Thanks to Ivan Auger <ivan.auger@wadsworth.org>) 6613572Spst 67