802.11 Wireless Networks: The Definitive Guide by Matthew Gast This errata page lists errors outstanding in the most recent printing. If you have technical questions or error reports, you can send them to booktech@oreilly.com. Please specify the printing date of your copy. This page was updated September 22, 2005. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification Confirmed errors: (throughout) Throughout book; 802.1X is consistently referred to as "802.1x" throughout the book. When IEEE specifications are standalone, the letter is capitalized, as in 802.1X. When a specification is an addition that will eventually be rolled up into its parent, the letter is lowercase. 802.11b modified clauses in 802.11, so its letter is lowercase. {43} Under "Backoff with the DCF"; In 2nd line under this heading, "congestion-based data" should be "contention-based data" (62) First paragraph after heading, "Multirate Support"; The second sentence is missing some text: "Speed nogotiation is particularly that are available to stations." It should say: "Speed negotiation is particularly important in wireless LANs because of the plethora of modulations and data rates which are available to stations." (77) 2nd sentence under "DS Parameter Set" "High-rate, distribution ststem networks use the same channels..." should be: "High-rate, distribution ststem networks use the same channels..." [80] Figure 4-39; The Beacon frame does not show the Supported Rates information element, which is required as per clause 7.2.3.1 of 802.11-1999. [81] Figure 4-41; Same mistake as on page 80 Probe Response frame should also include the Supported Rates Information Element. [111] Section Keying; The book says that two WEP keys are used by 802.1X. That is correct, but the description of how the keys are used is wrong. The book states that one key is used for upstream transmissions, and one is used for downstream transmissions. The correct implementation is that one key is used for unicast transmissions, and the second key is used for broadcast transmissions. (123) Figure 7-6; The process is called preauthentication, but the text in the figure refers to preauthorization. The figure should be changed to preauthentication to match the surrounding text {128+} Entire section; Buffering is only performed on frames with the Order bit clear. Frames sent using the StrictlyOrdered class are not allowed to be buffered at the access point. This minor distinction does not appear in the text. (154) Middle of the page; Heading reads "TKI P data transmission". Should be "TKIP data transmission" {191} Figure 10-26; The HR/DSSS PLCP framing diagram shows the length and CRC fields to be a mixture of 8 and 16 bits. Whereas the standard specifies them as all 16 bits. AUTHOR: Yes, that is correct. Both the length and CRC fields should be 16 bits. There are three changes necessary--I did get the CRC field length right in the "short preamble" bar at the bottom of the figure, but the length field is wrong. Both the CRC and length field are wrong in the "long preamble" bar at the top. [235] at the bottom of page; Equation at the bottom of the page must be Path loss (dB) = 32.5 + 20 log F + 20 log d instead of Path loss (dB) = 32.5 + 20 log F + log d