From nobody Wed Mar 02 17:45:09 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 521F619FB8DB for ; Wed, 2 Mar 2022 17:45:14 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K81jP2w6pz4ZNQ for ; Wed, 2 Mar 2022 17:45:13 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from smtpclient.apple (unknown [IPv6:2a00:20:705d:3bcd:285d:434a:1ed4:e8c8]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 09B46721E2808; Wed, 2 Mar 2022 18:45:09 +0100 (CET) Content-Type: text/plain; charset=us-ascii List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Subject: Re: em(4) does not autonegotiate when fixed media is set From: tuexen@freebsd.org In-Reply-To: <20220302120421.3c4d24e1@opal.com> Date: Wed, 2 Mar 2022 18:45:09 +0100 Cc: Lutz Donnerhacke , freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5B84E909-A7DD-4BC8-9395-F2C157FD273E@freebsd.org> References: <20220302103331.3a50e443@opal.com> <20220302162122.GA23140@belenus.iks-jena.de> <20220302120421.3c4d24e1@opal.com> To: "J.R. Oldroyd" X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4K81jP2w6pz4ZNQ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 193.175.24.27 is neither permitted nor denied by domain of tuexen@freebsd.org) smtp.mailfrom=tuexen@freebsd.org X-Spamd-Result: default: False [-2.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEFALL_USER(0.00)[tuexen]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all:c]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.86)[-0.856]; FROM_NO_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-net]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[193.175.24.27:from] X-ThisMailContainsUnwantedMimeParts: N > On 2. Mar 2022, at 18:04, J.R. Oldroyd wrote: >=20 > On Wed, 2 Mar 2022 17:21:22 +0100 Lutz Donnerhacke = wrote: >>=20 >> On Wed, Mar 02, 2022 at 04:40:38PM +0100, tuexen@freebsd.org wrote: >>> Is that what is expected? When using the above command I would = expect >>> that 100MBit/sec is used, not that the card negotiates with the peer >>> something else. But my expectations might be wrong... =20 >>=20 >> Negotation of a given subset is useful. Some devices do not work = without >> negotiation enabled, others refuse to work in this case. Standard = requires >> autonegotiation for 1000TX, recommends it for lower speeds (otherwise = assume >> half duplex). For 1000FX the situation is unclear, depends on the = year the >> device was manufactured ... Today autoneg is expected on all = interfaces even >> with a limited subset of capabilies. >>=20 >=20 > The patch enables autonegotiation for just the configured setting, not = full > autonegotiation. The intent is to let the other end know that we only = have > the one configured setting. >=20 > At present, the other end appears to be syncing to the 100baseTX speed = but > it does indeed appear to be choosing half-duplex, so the link does not = work > when the FreeBSD end has been configured for full-duplex. >=20 > The only thing I am not sure about is whether or not the = wait_to_complete > parameter should be cleared in this case. I suspect it should be. = There > is the case that the other end may not attempt any autonegotiation = dialog > either, and we do not want to hang waiting for it. I am not able to = test > this situation, though. OK, I see. Thanks a lot for the clarification. Best regards Michael >=20 > -jr