Garrett D'Amore writes: > Steven Stallion wrote: > > Okay, so lets say that en_10fdx_cap and en_100hdx_cap are set; does > > this affect negotiation? Is there a heuristic for choosing the correct > > cap? > Yes. 802.3 defines a preference ordering... 100fdx selected first, then > 100hdx, then 10fdx, then 10hdx. I can't recall where 100T4 fits in, but > I've yet to see a device that supports 100T4 and any of the others, so > its kind of irrelevant. (ISTR that 100T4 got priority over the other > 100base-T modes because the designers were concerned that 100T4 might be > *necessary* to operate over Category 3 cable.)
Just for the record (not that anyone cares) but the actual order within the 100Mbps series is 100BASE-T2 fdx first, then -TX fdx, then -T2 hdx, -T4 hdx, and finally -TX hdx. T2 is first because it runs over a "broader spectrum of copper cabling." TX is last because it has the most restrictive cabling. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
