I can confirm Brandon's comments (re: 802.3 speed/duplex negotiation not working properly with Cisco equipment). At Best, we had to force duplex and speed on both our Catalysts and our BSD boxes, otherwise, mysterious problems would occur (slow transfer rates in one direction, input or output errors, etc.). I'm sure Matt Dillon can attest to this as well. I highly doubt it's specific to the xl driver, or even 3Com cards, since 4-5 months ago I had such issues connecting a Catalyst to an HP ProCurve switch -- again, had to force the speed and duplex on both ends. I think this is a pretty "historic" problem with Cisco equipment. Look around the Web and you'll see what I mean. The procedure, if I remember right: Cat> set port x/y speed 100 Cat> set port x/y duplex full Cat> set port disable x/y BSD> ifconfig xl0 ... media 100baseTX mediaopt full-duplex BSD> [see note] Cat> set port enable x/y NOTE: Occasionally I'd also see this procedure fail until the BSD box was actually *rebooted*. This problem always eluded me, but may have changed severely since the days of 2.2.8 ( :) ). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Tue, Sep 07, 2004 at 11:36:57AM -0400, Brandon S. Allbery KF8NH wrote: > On Tue, 2004-09-07 at 11:19, Gleb Smirnoff wrote: > > On Tue, Sep 07, 2004 at 05:14:47PM +0200, Matthias Andree wrote: > > M> Hum, is the duplex setting manual? I've only used the 3C900 Combo for > > M> 10base2/BNC (Coax) so far. My DSL modem is hooked up to a "classic" > > M> (=old) 3C905 via crossover CAT5. > > > > The card I've acquired 15 minutes ago :) is 3C905-TX. It is connected > > with help of crossover CAT5 to my notebook. I run PPPoE server on > > notebook and can connect from desktop to this using ng_pppoe on > > CURRENT. > > We have occasionally seen what I am told by our network folks are odd > autonegotiation issues with 3C905-TX cards connected to Cisco switches, > for what it's worth. I'm not convinced it's solely a hardware issue, > though, as it seems to be a lot more common with "recent" 2.4-series > SuSE Linux kernels than with older ones. So far I've not had a chance > to try it with FreeBSD (and I'm unlikely to do so any time soon; around > here a stable AFS client is an absolute necessity...). > > -- > brandon s. allbery [linux,solaris,freebsd,perl] allbery_at_kf8nh.com > system administrator [WAY too many hats] allbery_at_ece.cmu.edu > electrical and computer engineering, carnegie mellon univ. KF8NH > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Tue Sep 07 2004 - 14:18:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:10 UTC