| Problems (3229) | Problems (13572) |
|---|---|
| 1 2Common problems and ways to work around them: 3 | 1 2Common problems and ways to work around them: 3 |
| 4Bootpd complains: "bind: Address already in use" and fails to start. 5 You are already running something that has bound the 6 BOOTP listening port number. Check /etc/inetd.conf or 7 the equivalent for a bootp line (or in startup files). 8 |
|
| 4Bootpd complains that it "can not get IP addr for HOSTNAME" 5 6 If the entry is a "dummy" (not a real host) used only for 7 reference by other entries, put '.' in front of the name. 8 9 If the entry is for a real client and the IP address for 10 the client can not be found using gethostbyname(), specify 11 the IP address for the client using numeric form. --- 28 unchanged lines hidden (view full) --- 40 41My bootp clients are given responses with a boot file name that is 42not a fully specified path. 43 44 Make sure the TFTP directory or home directory tags are set: 45 :td=/tftpboot: (or) 46 :hd=/usr/boot: (for example) 47 | 9Bootpd complains that it "can not get IP addr for HOSTNAME" 10 11 If the entry is a "dummy" (not a real host) used only for 12 reference by other entries, put '.' in front of the name. 13 14 If the entry is for a real client and the IP address for 15 the client can not be found using gethostbyname(), specify 16 the IP address for the client using numeric form. --- 28 unchanged lines hidden (view full) --- 45 46My bootp clients are given responses with a boot file name that is 47not a fully specified path. 48 49 Make sure the TFTP directory or home directory tags are set: 50 :td=/tftpboot: (or) 51 :hd=/usr/boot: (for example) 52 |
| 53My PC clients running Sun's PC-NFS Pro v1.1 fail to receive 54acceptable responses from the bootp server. 55 56 These clients send a request with the DHCP "message length" 57 option and the (new) BOOTP "broadcast flag" both set. 58 The bootp server (on SunOS) will send a fragmented reply 59 unless you override the length with :ms=1024: (or less). 60 The "broadcast flag" is not yet supported, but there is 61 a simple work-around, just add :ra=255.255.255.255: 62 for any clients that need their reply broadcasted. 63 You may need to use a differnet broadcast address. 64 (Thanks to Ivan Auger <ivan.auger@wadsworth.org>) 65 |
|