From owner-freebsd-net@FreeBSD.ORG Tue Jan 11 20:16:24 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 67A261065698 for ; Tue, 11 Jan 2011 20:16:24 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id CC7BA8FC1A for ; Tue, 11 Jan 2011 20:16:23 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id p0BJai3U038162; Tue, 11 Jan 2011 20:36:44 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id p0BJai0p038161; Tue, 11 Jan 2011 20:36:44 +0100 (CET) (envelope-from marius) Date: Tue, 11 Jan 2011 20:36:44 +0100 From: Marius Strobl To: Lev Serebryakov Message-ID: <20110111193644.GA38072@alchemy.franken.de> References: <1512738982.20110111124729@serebryakov.spb.ru> <122467803.20110111135330@serebryakov.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <122467803.20110111135330@serebryakov.spb.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, Yamagi Burmeister 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 20:16:24 -0000 On Tue, Jan 11, 2011 at 01:53:30PM +0300, Lev Serebryakov wrote: > Hello, Yamagi. > You wrote 11 ?????? 2011 ?., 13:30:23: > > > Hi, > > I've got several Hetzner EQ4 and on all these machines FreeBSD 8.1 runs > > just fine. I've never seen this strange negotiation problem myself. But > > maybe I was just lucky and got working mainboard and nic combinations. > > So if further information is needed, I'm happy to provide it. > It is known, that problems are in DC 13 and everything wotrks fine > in DC 11 and DC 12. > > I've discussed this problem in local (Russian-speaking) FreeBSD > community, and there are several people in DC 13 who HAVE these > problems and found different solutions, but all non-technical ones: > order gigabit connectivity, or pay for moving servers to other (old) > DCs... > If the latter means that the servers are physically moved as opposed to a new one being allocated this implies that re(4)/rgephy(4) isn't the sole factor responsible for this problem. In any case it would be helpful to have the corresponding dmesg bits as the Linux counterpart does some black magic for certain hardware versions when setting the media manually but re(4) doesn't which might be relevant in this scenario. Marius