From owner-freebsd-net@FreeBSD.ORG  Wed Aug  5 20:55:50 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 6D3D7106564A;
	Wed,  5 Aug 2009 20:55:50 +0000 (UTC)
	(envelope-from davidch@broadcom.com)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19])
	by mx1.freebsd.org (Postfix) with ESMTP id 446748FC13;
	Wed,  5 Aug 2009 20:55:49 +0000 (UTC)
Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.3.2)); Wed, 05 Aug 2009 12:54:48 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
	IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Wed, 5
	Aug 2009 12:54:47 -0700
From: "David Christensen" <davidch@broadcom.com>
To: "Jack Vogel" <jfvogel@gmail.com>, "Julian Elischer" <julian@elischer.org>
Date: Wed, 5 Aug 2009 12:54:46 -0700
Thread-Topic: em(4): sending ARP regardless of NOARP flag
Thread-Index: AcoVLgrkAgvkwClYTrmKhTutGZsmdAA1+OaQ
Message-ID: <5D267A3F22FD854F8F48B3D2B523819339EC3813D2@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <4A773D09.3030404@delphij.net>
	<2a41acea0908041011kaba6ab0ra6fec3b309fc42ef@mail.gmail.com>
	<4A786E80.5020201@elischer.org>
	<2a41acea0908041102h4249faa4r8db4f9178f0ca172@mail.gmail.com>
In-Reply-To: <2a41acea0908041102h4249faa4r8db4f9178f0ca172@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 66673C0260067309361-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Jack F Vogel <jfv@freebsd.org>,
	"freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
	"d@delphij.net" <d@delphij.net>
Subject: RE: em(4): sending ARP regardless of NOARP flag
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 20:55:50 -0000

> >> I don't see how arping or not can be a driver problem, the driver=20
> >> just sends packets queued by the stack, there exists NO=20
> mechanism to=20
> >> communicate that kind of thing down into the driver, -arp is=20
> >> something that must be negotiated in the stack somewhere,=20
> as for it=20
> >> working with broadcom...
> >> <shrugs>
> >>
> >>
> > except for the system management stuff.

On the bce(9) driver does it display the "MFW" flag during
driver load?  That would indicate whether NC-SI style management
firmware is running which would be unexpected on a NIC card.
If the Intel LOM is connected to a baseboard management controller
or service processor then the BMC or SP are likely generating
the ARP.  What's the source MAC address of the ARP?  Does it
match the LOM's MAC address or the MAC address of any BMC or SP?
The latter would generally be printed on a tag on the system or
perhaps in a BMC setup screen visible during POST.

Dave=