From owner-freebsd-net@FreeBSD.ORG Tue Jan 11 19:29:17 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 8B524106564A for ; Tue, 11 Jan 2011 19:29:17 +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 468928FC12 for ; Tue, 11 Jan 2011 19:29:17 +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 6424113DF5F; Tue, 11 Jan 2011 22:29:15 +0300 (MSK) Date: Tue, 11 Jan 2011 22:29:13 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <76226157.20110111222913@serebryakov.spb.ru> To: Brian Reichert In-Reply-To: <20110111163825.GF7511@numachi.com> References: <1512738982.20110111124729@serebryakov.spb.ru> <20110111163825.GF7511@numachi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable 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 19:29:17 -0000 Hello, Brian. You wrote 11 =FF=ED=E2=E0=F0=FF 2011 =E3., 19:38:25: >> 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? I don't know, I never work with Juniper e3k switches (And any other Juniper products at all). All I know, that older Juniper Switches in not-so-new DCs of same provider doesn't have this problem, and, on other hand, Linux and Windows 2008 don't have problems with new ones too. > If they're doing so by disabling autonegotiation, then that's where > some grief may come from. Linux work with autonegotiation, as I can see (It is outpuit from Rescue Linux system on SAME my server, where FreeBSD shows half-duplex even if forced to full-duplex): root@rescue ~ # mii-tool -v eth0 eth0: 100 Mbit, full duplex, link ok product info: vendor 00:07:32, model 17 rev 2 basic mode: 100 Mbit, full duplex basic status: link ok capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT= -FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 100baseTx-HD root@rescue ~ # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@rescue ~ # So, it seems, that autonegotiation is disabled, but it works for Linux, and manual setting of media and mediaopt doesn't help FreeBSD. Also, please note, that when port is in 1Gib mode (which can be buyed for additional money, which I can not afford) FreeBSD works fine. --=20 // Black Lion AKA Lev Serebryakov