Talk:Late collision
 | The contents of the Late collision page were merged into Carrier sense multiple access with collision detection on 2015-07-27. For the contribution history and old versions of the merged article please see its history. |
Causes
[edit]What are the causes of late collisions?
- usually over 100 meter runs that have enough traffic to create a collision... the collision detection will be indicated but due to the length of the run will be rec'd late after waiting to hear about it and after the next packet(s) are sent.
- the question i have about late collisions though is, "will putting a switched hub on both sides of a run over 100 meters (say 400 meters), eliminate all collision and thus let you safely break the 100 meter rule?"
Duplex mismatch
[edit]Interestingly the full/half duplex mismatch cause listed on the page is flatly contradicted by Cisco's ICND1 study materials, which state that "Incorrect duplex settings do not cause late collisions." —Preceding unsigned comment added by 12.217.86.174 (talk) 19:44, 13 March 2009 (UTC)
- Incorrect duplex settings will cause a late collision from the perspective of the half duplex end of the link because the full duplex end thinks it can transmit at any time. Plugwash (talk) 14:07, 13 January 2012 (UTC)