From owner-freebsd-bugs Thu Feb 15 14:20:11 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 C3BD837B4EC for ; Thu, 15 Feb 2001 14:20:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1FMK8Z86120; Thu, 15 Feb 2001 14:20:08 -0800 (PST) (envelope-from gnats) Date: Thu, 15 Feb 2001 14:20:08 -0800 (PST) Message-Id: <200102152220.f1FMK8Z86120@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Young, Jason" Subject: Re: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow f ull-duplex<->half-duplex communication Reply-To: "Young, Jason" 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: "Young, Jason" To: "'freebsd-gnats-submit@FreeBSD.org'" , "'klui@cup.hp.com'" Cc: Subject: Re: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow f ull-duplex<->half-duplex communication Date: Thu, 15 Feb 2001 12:05:22 -0600 If there's a duplex mismatch, your symptoms would seem to indicate it would have to be on your work machine, between it and your switch. You have proven (with the transfer from the HPUX machine to your home machine) that your home machine has reasonable connectivity. This could definitely be caused by the OS upgrade, since it seems that the driver plays a very large role in speed and duplex negotiations and you've changed drivers. You haven't mentioned how you know that link is 10BaseT full-duplex. Is this an assumption, or have you set it on the switch personally or otherwise know it's supposed to be full-duplex? You could quickly check if this is the problem by doing this: ifconfig pcn0 media 10BaseT mediaopt half-duplex Then test your connectivity again. If that fixes things, the switch wasn't really giving you full duplex connectivity. If the switch is set to autonegotiate duplex settings, be aware this tends to fail a lot and you'll probably need to force the setting to be whichever way you want it or stay half duplex. If autonegotiation worked before in 3.2-RELEASE with the same hardware with the lnc driver, you may want to send a (very, very, very, very) detailed bug report to Bill Paul (wpaul@freebsd.org), who maintains that driver. Jason Young CNS - Network Design, Anheuser-Busch (314)577-4597 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message