1 2[ Old announcement from version 2.2: ] 3 4New features in version 2.2 include: 5 6o 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 10o 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 16o 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 21o 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 29o 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 35Bug fixes in this version include: 36 37o 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 41o A bug in comparing subnet masks has been fixed. 42 43o A bug in calculating the size of the vendor information area when 44 inserting the hostname has been fixed. 45 46 47Other changes: 48 49o 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 54[ Old announcement from version 2.1: ] 55 56Subject: Updated RFC1048 BOOTP server now available 57 58Well, no surprise, bootpd 2.0 had a few bugs. A new improved version, 59bootpd 2.1, is now available for anonymous FTP from lancaster.andrew.cmu.edu 60(128.2.13.21). The new server can be found in pub/bootp.2.1.tar. 61 62Bug fixes and improvements in version 2.1 include: 63 64o The definition of "access to the bootfile" has been changed to require the 65 public read access bit to be set. This is required by tftpd(8), so the 66 server will not reply with a file which a client cannot obtain via TFTP. 67o The RFC1084 bootfile size tag has been implemented. It allows either 68 automatic or manual specification of the bootfile size in 512-octet blocks. 69o Generic tags now work as advertised. 70o A subtle bug which caused strange parsing behavior under certain conditions 71 has been fixed. 72o The RFC1048 vendor information now has the correct byte order on 73 little-endien machines such as the VAX. 74o Failure to specify the bootfile home directory and/or default bootfile in 75 the configuration file no longer causes server crashes. The server now 76 makes a reasonably intelligent choice if this configuration information is 77 missing. This is documented in the man page. 78o BOOTP requests from clients which already know their IP addresses no longer 79 cause server crashes. 80 81 82Please direct questions, comments, and bug reports to 83Walt Wimer <ww0n@andrew.cmu.edu> or Drew Perkins <ddp@andrew.cmu.edu>. 84[ Changed: now please send mail to: <bootp@andrew.cmu.edu> ] 85 86 87Good luck, 88 89Walt Wimer 90Network Development 91Carnegie Mellon University 92 93 94[ Old announcement from version 2.0: ] 95 96Subject: RFC-1048 compatible BOOTP server now available 97 98 99An RFC-1048 (BOOTP Vendor Information Extensions) compatible BOOTP (RFC-951) 100server is now available for anonymous FTP from lancaster.andrew.cmu.edu 101(128.2.13.21). The new server can be found in pub/bootp.2.0.tar. This is 102an enhanced version of the existing CMU BOOTP server which was derived from 103the original BOOTP server created by Bill Croft at Stanford. 104 105New features and changes in version 2.0 include: 106 107o Full support for the vendor information extensions described in RFC-1048. 108o Faster response time (host lookup via hash table instead of linear search). 109o New termcap-like configuration file format which allows greater flexibility 110 in specifying the variable vendor information of RFC-1048. Host entries 111 may refer to other hosts as templates so that redundant information need 112 be specified only once. 113o Continued support for the CMU vendor information format. The server may 114 be configured on a per-host basis to always reply with a certain vendor 115 information format or to reply based on the client's request. 116o Expanded logging. 117o The server may now be run by inetd or as a standalone program like the 118 old version. 119o The configuration and debugging dump files may be specified on the command 120 line. 121 122 123The server has been successfully tested on the following machines: 124 125 IBM RT PC running ACIS 4.3 (4.3 BSD) 126 Sun 3/50 running SunOS 3.5 127 DEC MicroVAX II running Ultrix 1.1 128 DEC MicroVAX II running Ultrix 2.2 129 130 131Please direct questions, comments, and bug reports to 132Walt Wimer <ww0n@andrew.cmu.edu> or Drew Perkins <ddp@andrew.cmu.edu>. 133[ Changed: now please send mail to: <bootp@andrew.cmu.edu> ] 134 135 136Sincerely, 137 138Walt Wimer 139Network Development 140Carnegie Mellon University 141 142