1 2 [ Old announcement from version 2.2: ] 3 4 New features in version 2.2 include: 5 6 o A new "td" tag allows the specification of a "TFTP directory" for use 7 with so-called "secure" implementations of tftpd which chroot(2) to a 8 particular directory. 9 10 o A new "sa" tag allows the explicit specification of the TFTP 11 "server address." Formerly, the 'siaddr' field of the BOOTREPLY was 12 always filled with the IP address of the BOOTP server. The "sa" tag 13 now allows the BOOTP server and the TFTP server to be two different 14 machines, if desired. 15 16 o The server now automatically determines whether it is running as a 17 standalone program (e.g. invoked by hand from a shell) or as a child of 18 /etc/inetd. The -s option and a new -i option are provided to force 19 standalone or inetd mode if necessary. 20 21 o When the vendor magic cookie is zero, BOOTP replies now default to the 22 RFC 1084 vendor format, rather than the old CMU format. This helps 23 interoperability with uncooperative BOOTP clients which want RFC 1084 24 format but don't bother filling in the magic cookie properly to tell 25 the server... *sigh* (This makes the ":vm=rfc1048:" tag unnecessary 26 in most cases now. Oh, the "vm" tag now accepts "rfc1084" as well as 27 "rfc1048" -- they mean the same thing.) 28 29 o Log messages now include the specific network type. For example, rather 30 than saying "request from hardware address ABCDEF012345", the message is 31 now "request from Ethernet address ABCEDF012345", or "request from 32 IEEE802 address 4000A1B2C3D4". 33 34 35 Bug fixes in this version include: 36 37 o The automatic bootfile-size calculation now works correctly when the 38 file size is an exact multiple of 512 octets. It used to return a number 39 which was one 512-octet unit greater than necessary. 40 41 o A bug in comparing subnet masks has been fixed. 42 43 o A bug in calculating the size of the vendor information area when 44 inserting the hostname has been fixed. 45 46 47 Other changes: 48 49 o The man page has been split into two man pages. One covers the server 50 itself (bootpd.8) and the other covers the configuration file format 51 (bootptab.5). 52 53 55 [ Old announcement from version 2.1: ] 56 57 Subject: Updated RFC1048 BOOTP server now available 58 59 Well, no surprise, bootpd 2.0 had a few bugs. A new improved version, 60 bootpd 2.1, is now available for anonymous FTP from lancaster.andrew.cmu.edu 61 (128.2.13.21). The new server can be found in pub/bootp.2.1.tar. 62 63 Bug fixes and improvements in version 2.1 include: 64 65 o The definition of "access to the bootfile" has been changed to require the 66 public read access bit to be set. This is required by tftpd(8), so the 67 server will not reply with a file which a client cannot obtain via TFTP. 68 o The RFC1084 bootfile size tag has been implemented. It allows either 69 automatic or manual specification of the bootfile size in 512-octet blocks. 70 o Generic tags now work as advertised. 71 o A subtle bug which caused strange parsing behavior under certain conditions 72 has been fixed. 73 o The RFC1048 vendor information now has the correct byte order on 74 little-endien machines such as the VAX. 75 o Failure to specify the bootfile home directory and/or default bootfile in 76 the configuration file no longer causes server crashes. The server now 77 makes a reasonably intelligent choice if this configuration information is 78 missing. This is documented in the man page. 79 o BOOTP requests from clients which already know their IP addresses no longer 80 cause server crashes. 81 82 83 Please direct questions, comments, and bug reports to 84 Walt Wimer <ww0n (a] andrew.cmu.edu> or Drew Perkins <ddp (a] andrew.cmu.edu>. 85 [ Changed: now please send mail to: <bootp (a] andrew.cmu.edu> ] 86 87 88 Good luck, 89 90 Walt Wimer 91 Network Development 92 Carnegie Mellon University 93 94 96 [ Old announcement from version 2.0: ] 97 98 Subject: RFC-1048 compatible BOOTP server now available 99 100 101 An RFC-1048 (BOOTP Vendor Information Extensions) compatible BOOTP (RFC-951) 102 server is now available for anonymous FTP from lancaster.andrew.cmu.edu 103 (128.2.13.21). The new server can be found in pub/bootp.2.0.tar. This is 104 an enhanced version of the existing CMU BOOTP server which was derived from 105 the original BOOTP server created by Bill Croft at Stanford. 106 107 New features and changes in version 2.0 include: 108 109 o Full support for the vendor information extensions described in RFC-1048. 110 o Faster response time (host lookup via hash table instead of linear search). 111 o New termcap-like configuration file format which allows greater flexibility 112 in specifying the variable vendor information of RFC-1048. Host entries 113 may refer to other hosts as templates so that redundant information need 114 be specified only once. 115 o Continued support for the CMU vendor information format. The server may 116 be configured on a per-host basis to always reply with a certain vendor 117 information format or to reply based on the client's request. 118 o Expanded logging. 119 o The server may now be run by inetd or as a standalone program like the 120 old version. 121 o The configuration and debugging dump files may be specified on the command 122 line. 123 124 125 The server has been successfully tested on the following machines: 126 127 IBM RT PC running ACIS 4.3 (4.3 BSD) 128 Sun 3/50 running SunOS 3.5 129 DEC MicroVAX II running Ultrix 1.1 130 DEC MicroVAX II running Ultrix 2.2 131 132 133 Please direct questions, comments, and bug reports to 134 Walt Wimer <ww0n (a] andrew.cmu.edu> or Drew Perkins <ddp (a] andrew.cmu.edu>. 135 [ Changed: now please send mail to: <bootp (a] andrew.cmu.edu> ] 136 137 138 Sincerely, 139 140 Walt Wimer 141 Network Development 142 Carnegie Mellon University 143 144
Indexes created Thu Sep 25 16:09:42 GMT 2025