Date: Wed, 14 Aug 2002 19:17:43 -0400 From: Barney Wolff <barney@tp.databus.com> To: Matt Johnson <mattj@maine.rr.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problems with the xl driver or 3Com cards? Message-ID: <20020814231743.GA34534@tp.databus.com> In-Reply-To: <B6212201-AFD6-11D6-8FEA-00306585BF9A@maine.rr.com> References: <B6212201-AFD6-11D6-8FEA-00306585BF9A@maine.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I can think of some possibilities: 1. Duplex mismatch - are you sure the card knows it's on a full-duplex port? If the switch is managed or has lights, what does it say about it? Try varying the media-opt setting to ifconfig. What does ifconfig xl0 say? 2. What are you using for a tcp receive window? sysctl net.inet.tcp.recvspace will tell you. Sometimes, one that's too big will cause overruns, especially if the card shares an IRQ with something else. 3. Try moving the nic to a different slot, which can change the assigned IRQ. You can detect problems of packet loss by looking at netstat -s on both sender (for retransmissions) and receiver (for duplicate packets). On Wed, Aug 14, 2002 at 06:34:27PM -0400, Matt Johnson wrote: > > I've tried everything, and I'm really lost for answers here. I have a > FreeBSD box which has a 3Com Etherlink XL in it. A while back, I got a > new 100mbps switch to replace my old 10mbps hub. I noticed that despite > now having a faster network hub, my FreeBSD machine was still unable to > get speeds of more than 200 or 300K/s. This only happened when the > FreeBSD machine was receiving. Transmitting worked fine. -- Barney Wolff I'm available by contract or FT: http://www.databus.com/bwresume.pdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020814231743.GA34534>