From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 05:19:24 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B009E16A4CE for ; Tue, 22 Mar 2005 05:19:24 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3207B43D2D for ; Tue, 22 Mar 2005 05:19:24 +0000 (GMT) (envelope-from gary.smithe@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1603416wra for ; Mon, 21 Mar 2005 21:19:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=RWW5LsC8Dk+oGxZaQ5YIGH6YwMVo/aI+71n4z0QMZc8ZQIaizr2XIcOH5oS8ENg7gZHsFq4ZPySPFOXeDq6wZ+KghUq1wz7eKtvd8YFskq6dHTACMVEFK0HQGDjfLF2Vo918Yho0VsvmONfxIyUzJIRYCDgFEUVHDwcODL8ubsA= Received: by 10.54.23.69 with SMTP id 69mr929374wrw; Mon, 21 Mar 2005 21:19:23 -0800 (PST) Received: by 10.54.41.29 with HTTP; Mon, 21 Mar 2005 21:19:22 -0800 (PST) Message-ID: Date: Mon, 21 Mar 2005 23:19:22 -0600 From: Gary Smithe To: freebsd-questions@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: Subject: Re: NIC won't DHCP or configure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Smithe List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 05:19:24 -0000 On Mon, 21 Mar 2005 10:54:24 -0800, Andrew Robinson wrote: > Hello FreeBSD community, > > I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. > > (I also tried the February Stable, with no change as far as I can tell). > > WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. > > My FreeBSD kernel is generic, and both the following lines are uncommented: > > device miibus # MII bus support > device re # RealTek 8139C+/8169/8169S/8110S > > The output from ifconfig is: > > fwe0: flags=108802 mtu 1500 > options=8 > ether 02:90:f5:40:24:d8 > ch 1 dma -1 > plip0: flags=108810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > and what I think is the relevant part of dmesg is: > > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 > fwe0: Ethernet address: 02:90:f5:40:24:d8 > fwe0: if_start running deferred for Giant > > It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? > > Thanks much! > > Andrew > My advice, try a different network switch / hub. Read on to find out why. Trying to do the poor man's "Norton Ghost" at a local school for a WinXP lab (using dd over ssh), I had some stupid issues. The NIC in question was an onboard SiS 900. Here's what I had using various "live-cd" distros: winxp (installed) - i got an IP address knoppix and DSL (both debian) - I got an IP address System Rescue CD (gentoo) - no address g4u and obsd live cd (obsd) - no address (never did try fbsd, but obsd is fairly close) When I moved a sample PC closer to the DHCP server, every distro above got an address. The lab has an older d-link 24 port switch. There are 4 switches total between the lab and the dhcp server. When I moved the PC, it was then connected to a netgear 5-port 100mb switch, still about 4 switches away from the dhcp server. I tried setting an address with ifconfig for each of the failing distros, with no success. I vaguely remember getting some weird issues reagarding the PHY in obsd... I have no idea what the cause is (just discovered this last week), but am strongly suspicious of the d-link switch. I'm going to replace it (assuming funds are available) soon. Just thought I'd pass it on, in case it helps. GS