From owner-freebsd-net@FreeBSD.ORG Mon Apr 2 10:32:33 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4512E1065675 for ; Mon, 2 Apr 2012 10:32:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 11B5C8FC1A for ; Mon, 2 Apr 2012 10:32:32 +0000 (UTC) Received: by dadz14 with SMTP id z14so10285053dad.17 for ; Mon, 02 Apr 2012 03:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ndPVa3iSUx71ip+CYM6daRpfAHPp7NV2Ycgv58y+psI=; b=nQDD4g589yJxfIEc53h3jnMHFC+j/hLBbR0UcwdswksYM796YQKH1udCoVLUYxZ8QC 7mym2RUzYL8qi9xOI7A0OIY4rTNkjW3r/HEj0obqLckkHVEY5Wef3a+OSOuY3GPm34Wp SW9dbl3D6QdSZPze7lJvkVfkJI+rVbDeOUfgxkiwaYaNwm616niLaLVy9chcHoB8kytn 86MduG4a8ZG6wL5tEkPptia8EsUqVA5DPMG1qeIA1hQVqIDyboXBqqXuxfbO2DdbNGBh 1vBNdx5z+U+DHBPuhL1H/4LBIQGM40HBiLOLZ+t6NKr7grRlVfRLKjp1S100+H0v4tAJ lP7g== Received: by 10.68.237.36 with SMTP id uz4mr19731262pbc.165.1333362752663; Mon, 02 Apr 2012 03:32:32 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id z5sm13855976pbn.35.2012.04.02.03.32.30 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 Apr 2012 03:32:31 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 02 Apr 2012 19:32:25 -0700 From: YongHyeon PYUN Date: Mon, 2 Apr 2012 19:32:25 -0700 To: enoch Message-ID: <20120403023225.GD3571@michelle.cdnetworks.com> References: <20120330233819.GC7325@michelle.cdnetworks.com> <4F75C5EC.6090303@hotmail.com> <20120402195215.GA3571@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: [nfe] DHCP failure on 8-stable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 10:32:33 -0000 On Mon, Apr 02, 2012 at 03:50:02AM -0400, enoch wrote: > On 04/02/2012 03:52 PM, YongHyeon PYUN wrote: > > On Fri, Mar 30, 2012 at 10:40:44AM -0400, enoch wrote: > >> On 03/30/2012 19:38, YongHyeon PYUN wrote: > >>> On Fri, Mar 30, 2012 at 03:01:52AM -0400, enoch wrote: > >>>> Recently it became extremely difficult to pass the DHCP discovery step > >>>> on boot. Now I am using the buggy [nve] instead. > >>>> > >>>> Can anyone help? > >>>> > >>> > >>> Did you set synchronous_dhclient option in rc.conf? > >>> > >> > >> Yes: ifconfig_nfe0="SYNCDHCP" > >> > >> I guess [nfe] is undergoing gradual devel changes of some sort as before > >> it had some chance of reporting "empty headers" on initial ifconfig and > >> refusing to work. Sorry, I should have reported when encountering the > >> first problems rather than solve by reboot. > > > > Would you show me the output of both dmesg(nfe(4) and its PHY only) > > and 'sysctl dev.nfe.0.stats'? > > It would be also helpful to know whether nfe(4) still sees > > incoming traffic. > > Does assigning static IP work? > > > > Static IP direct communication attempt from this desktop to another > laptop through a crossover cable fails as follows. Thanks. > > nfe0: flags=8843 metric 0 mtu 1500 > options=82008 > ether 00:1f:bc:00:19:dc > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (1000baseT > ) > status: active > > nfe0: link state changed to UP > nfe0: port 0xf200-0xf207 > mem 0xefffb000-0xefffbfff irq 21 at device 20.0 on pci0 > miibus1: on nfe0 It seems you've omitted PHY driver here. What PHY driver was attached to nfe(4)? > nfe0: Ethernet address: 00:1f:bc:00:19:dc > nfe0: [FILTER] > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > nfe0: link state changed to UP > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > > dev.nfe.0.stats.rx.frame_errors: 0 > dev.nfe.0.stats.rx.extra_bytes: 0 > dev.nfe.0.stats.rx.late_cols: 0 > dev.nfe.0.stats.rx.runts: 0 > dev.nfe.0.stats.rx.jumbos: 0 > dev.nfe.0.stats.rx.fifo_overuns: 0 > dev.nfe.0.stats.rx.crc_errors: 0 > dev.nfe.0.stats.rx.fae: 0 > dev.nfe.0.stats.rx.len_errors: 0 > dev.nfe.0.stats.rx.unicast: 56 > dev.nfe.0.stats.rx.multicast: 0 > dev.nfe.0.stats.rx.broadcast: 280 > dev.nfe.0.stats.tx.octets: 7517 > dev.nfe.0.stats.tx.zero_rexmits: 51 > dev.nfe.0.stats.tx.one_rexmits: 0 > dev.nfe.0.stats.tx.multi_rexmits: 0 > dev.nfe.0.stats.tx.late_cols: 0 > dev.nfe.0.stats.tx.fifo_underuns: 0 > dev.nfe.0.stats.tx.carrier_losts: 0 > dev.nfe.0.stats.tx.excess_deferrals: 0 > dev.nfe.0.stats.tx.retry_errors: 0 > Thanks. Would you show me the output of "pciconf -lcbv"? > >> > >> In any case, the alternative [nve] should be marked "dangerous" as under > >> heavy load it tends to crash the system. > >> > >> Thanks, Enoch. > >> > >>>> > >>>> uname -a > >>>> ~~~~~~~~ > >>>> FreeBSD dome 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #7: Thu Mar 29 > >>>> 14:37:00 EDT 2012 root@dome:/usr/obj/usr/src/sys/DOME amd64 > >>>> > >>>> nfe0 fails at DHCPDISCOVER. > >>>> > >>>> ifconfig: > >>>> > >>>> nfe0: flags=8843 metric 0 mtu 1500 > >>>> options=82008 > >>>> ether 00:1f:bc:00:19:dc > >>>> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > >>>> media: Ethernet autoselect (100baseTX ) > >>>> status: active > >>>> > >>>> lspci: > >>>> > >>>> 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) > > > > Because there are several MCP51 variants, "pciconf -lcbv" is more