Designing Large Scale LANs by Kevin Dooley The unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. 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 This page was updated June 16, 2003. UNCONFIRMED errors and comments from readers: {55} Ring topology section, 2nd para; You say that a device wants to send a packet to another on the same ring, the packet is sent downstream "until it reaches the destination". Later, in the same section, you say that the sender eventually receives the packet it sent, with a marking showing that the packet was received by the destination. These are contradictory statements. Also, you mix the usage of "frame" and "packet" in this section (55) 2nd para, 3rd line; Change "resister" to "resistor". (56) Star topology section, 1st. para, 2nd line; Change "to all of devices" to "to all devices". (57) Mesh Topology section label; Change "Mesh Topology" to "Mesh topology". This is the convention used in the section labels for the other topology possibilities. (89) Figure 3-16; The paragraph spanning pp 90-91 refers to segment 1 on Figure 3-16 (p 89), but the segments on Figure 3-16 aren't labelled. I figured it out from context, but at the expense of time and clarity. In the same paragraph, I don't understand how router Core B still has a valid connection to the segment if the fiber has been cut. [188] second paragraph; The 27 bit mask should be 255.255.255.224 The 30 bit mask should be 255.255.255.252 I think you have a made a typo in printing 255.255.224.0 and 255.255.252.0 - but a misleading typo.