From owner-freebsd-net@FreeBSD.ORG Tue Jan 11 17:05:08 2011 Return-Path: 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 A0F521065673 for ; Tue, 11 Jan 2011 17:05:08 +0000 (UTC) (envelope-from reichert@numachi.com) Received: from meisai.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.freebsd.org (Postfix) with SMTP id 1F8958FC18 for ; Tue, 11 Jan 2011 17:05:07 +0000 (UTC) Received: (qmail 89214 invoked by uid 1001); 11 Jan 2011 16:38:26 -0000 Date: Tue, 11 Jan 2011 11:38:25 -0500 From: Brian Reichert To: Lev Serebryakov Message-ID: <20110111163825.GF7511@numachi.com> References: <1512738982.20110111124729@serebryakov.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1512738982.20110111124729@serebryakov.spb.ru> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 17:05:08 -0000 On Tue, Jan 11, 2011 at 12:47:29PM +0300, Lev Serebryakov wrote: > Hello, Freebsd-net. > > Very large and famous (due to very attractive prices) hosting > provider Hetzner.de discards FreeBSD support on dedicated servers, > because these servers can niot negotiate 100Mbit/DUPLEX when > switches' ports are limited to 100Mbit (1Gbit connection costs > additional money) only under FreeBSD. Linux works fine. How are the switches being forced to 100/full? If they're doing so by disabling autonegotiation, then that's where some grief may come from. If it's not, then ignore the rest of this email. :) For certain hardware combos, I've seen even Linux servers (on Dell hardware) fail to autonegotiate properly. Here's the set of litany I trot out when I have to deal with customer's issues surrounding gigabit and autonegotiation: ------------- With the advent of 1000T networking, the specs says that autonegotation needs to be enabled: http://etherealmind.com/2008/07/15/ethernet-autonegotiation-works-why-how-standard-should-be-set/ " A major problem is that many people are also hard setting Gigabit Ethernet, and this is causing major problems. Gigabit Ethernet must have auto-negotiation ENABLED to allow negotiation of master / slave PHY relationship for clocking at the physical layer. Without negotiation the line clock will not establish correctly and physical layers problems can result." Further, this doc from Dell: http://www.dell.com/content/topics/global.aspx/power/en/ps1q01_hernan?c=us&cs=555&l=en&s=biz Cites: "In addition, the 1999 standard for Gigabit over copper cabling, IEEE Std 802.3ab, added the following enhancements to the Auto-Negotiation standard:" * Mandatory auto-negotiation for 1000BaseT * Configure master and slave modes for the PHY Further: http://en.wikipedia.org/wiki/Autonegotiation "The debatable portions of the autonegotiation specifications were eliminated by the 1998 version of IEEE 802.3. In 1999, the negotiation protocol was significantly extended by IEEE 802.3ab, which specified the protocol for gigabit Ethernet, making autonegotiation mandatory for 1000BASE-T gigabit Ethernet over copper." > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -- Brian Reichert 55 Crystal Ave. #286 Derry NH 03038-1725 USA BSD admin/developer at large