From owner-freebsd-bugs Fri Feb 2 16:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9000337B503 for ; Fri, 2 Feb 2001 16:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f130U4i56223; Fri, 2 Feb 2001 16:30:04 -0800 (PST) (envelope-from gnats) Date: Fri, 2 Feb 2001 16:30:04 -0800 (PST) Message-Id: <200102030030.f130U4i56223@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Lui Subject: Re: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow full-duplex<->half-duplex communication Reply-To: Ken Lui Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24811; it has been noted by GNATS. From: Ken Lui To: Bill Fumerola Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow full-duplex<->half-duplex communication Date: Fri, 2 Feb 2001 16:24:27 -0800 (PST) On Fri, 2 Feb 2001, Bill Fumerola wrote: > > >Description: > > I have a FreeBSD 4.2 installation at work over 10baseT at full duplex > > communicating with a FreeBSD 4.2 installation at home over 10baseT at > > half duplex. The office box is connected to a switch. The remote is > > connected to a hub via SDSL. If I copy files from the 4.2 box at work > > to the 4.2 box at home, I will inevitably get network stalls. Searching > > dejanews reveals that this may be caused by the interaction between a > > machine that is connected at full duplex versus one that is connected at > > half duplex. The work machine has used the following ethernet cards with > > the same results: PCNet-FAST/NCR 53c875 combination card (pcn driver) > > and 3Com 3c905B XL (xl driver). > > This is the fault of your hub. It is the responsibility of the hub to > translate those, its possible that your hub just simply has two busses > (one half-duplex, one full-duplex) or something like that. Since it works with another operating system and a prior version of FreeBSD, I find it difficult to believe my hub is the problem. Could you tell me how I can determine my hub is at fault? My hub is old and has a 10base2 connector, which I'm using for other boxes. But my FreeBSD 4.2 box is using 10baseT/UTP. I have never experienced these types of stalls until I began using FreeBSD 4.2. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message