From owner-freebsd-net@FreeBSD.ORG Tue Jan 11 19:41:42 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 E32EC106564A for ; Tue, 11 Jan 2011 19:41:42 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [80.249.188.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6B30D8FC17 for ; Tue, 11 Jan 2011 19:41:42 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 73D7B13DF5F; Tue, 11 Jan 2011 22:41:41 +0300 (MSK) Date: Tue, 11 Jan 2011 22:41:39 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <510035228.20110111224139@serebryakov.spb.ru> To: Marius Strobl In-Reply-To: <20110111193644.GA38072@alchemy.franken.de> References: <1512738982.20110111124729@serebryakov.spb.ru> <122467803.20110111135330@serebryakov.spb.ru> <20110111193644.GA38072@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable 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 19:41:43 -0000 Hello, Marius. You wrote 11 =FF=ED=E2=E0=F0=FF 2011 =E3., 22:36:44: >> 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 It is known, that DC 13 has new Juniper e3k switches, and older DCs have older Juniper equipment. > 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. Here it is from Rescue FreeBSD system: re0: port 0xe800-0x= e8ff mem 0xfbeff000-0xfbefffff,0xf8ff0000-0xf8ffffff irq 16 at device 0.0 o= n pci6 re0: Using 1 MSI messages re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX,= 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-= FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 6c:62:6d:a7:bb:37 re0: [FILTER] And, please note very strange output from Linux's mii-tool and ethtool in previous my message to list: mismatch between "basic mode" and "link partner". --=20 // Black Lion AKA Lev Serebryakov