From owner-freebsd-net@FreeBSD.ORG  Wed Jan 12 07:44:52 2011
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7D4F2106566B
	for <freebsd-net@freebsd.org>; Wed, 12 Jan 2011 07:44:52 +0000 (UTC)
	(envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
	by mx1.freebsd.org (Postfix) with SMTP id B16048FC13
	for <freebsd-net@freebsd.org>; Wed, 12 Jan 2011 07:44:51 +0000 (UTC)
Received: (qmail 84489 invoked from network); 12 Jan 2011 07:18:08 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
	by bizet.nethelp.no with SMTP; 12 Jan 2011 07:18:08 -0000
Date: Wed, 12 Jan 2011 08:18:08 +0100 (CET)
Message-Id: <20110112.081808.74670677.sthaug@nethelp.no>
To: reichert@numachi.com
From: sthaug@nethelp.no
In-Reply-To: <20110111195810.GH7511@numachi.com>
References: <76226157.20110111222913@serebryakov.spb.ru>
	<4D2CB1F5.6080106@aws-net.org.ua>
	<20110111195810.GH7511@numachi.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org, artem@aws-net.org.ua
Subject: Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI
 MoBo: problems with duplex negotiation (Hetzner host provider discard
 FreeBSD support due this bug)
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2011 07:44:52 -0000

> > May be linux driver defaults to full-duplex if autoneg fails?..
> 
> I've seen some Linux drivers fail back to half-duplex under these
> circumstances.
> 
> It may very well depend on driver version and hardware (firmware)?
> 
> I admit, I don't know what layer is responsible for handling
> autonegotiation...

It should be noted that fallback to half-duplex when autoneg fail is
actually *required* by the IEEE Ethernet standards. We may not like
it, but there it is...

Steinar Haug, Nethelp consulting, sthaug@nethelp.no