From owner-freebsd-net@FreeBSD.ORG Tue Aug 4 18:40:09 2009 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 5E2091065690 for ; Tue, 4 Aug 2009 18:40:09 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 2A6838FC12 for ; Tue, 4 Aug 2009 18:40:08 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n74Iciax008381; Tue, 4 Aug 2009 11:38:46 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 4 Aug 2009 11:37:26 -0700 Message-ID: In-Reply-To: <4A773D09.3030404@delphij.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: em(4): sending ARP regardless of NOARP flag Thread-Index: AcoUcpJpTWRcKMVzSfemDReHQiHO1gAv6BkQ References: <4A773D09.3030404@delphij.net> From: "Li, Qing" To: , "Jack F Vogel" Cc: freebsd-net@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 18:40:09 -0000 Is this on -CURRENT ? --Qing > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of Xin LI > Sent: Monday, August 03, 2009 12:40 PM > To: Jack F Vogel > Cc: freebsd-net@freebsd.org > Subject: em(4): sending ARP regardless of NOARP flag >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi, Jack, >=20 > I have observed that, even if -arp is specified when adding an IP > address to the em(4) interface, an ARP request is still being sent. > Here is a tcpdump from my network environment: >=20 > 11:15:01.370256 00:13:72:66:b5:d7 > ff:ff:ff:ff:ff:ff, ethertype ARP > (0x0806), length 60: Request who-has *.*.152.120 tell *.*.152.120, > length 46 > 11:15:01.370270 00:15:17:92:39:0e > 00:13:72:66:b5:d7, ethertype ARP > (0x0806), length 42: Reply *.*.152.120 is-at 00:00:5e:00:01:07, length > 28 >=20 > (The first ARP request was sent from a Dell branded Intel 82541EI based > NIC, the latter is from a cheaper server that is part of CARP > configuration which is unrelated to the problem in response to the ARP > request) >=20 > I was originally under the impression that there is some bug in our ARP > code but with a bce(4) card, the problem does not exist. After a > glance > at e1000 driver code, it looks like that the e1000 NIC has a feature of > hardware interception of ARP, can this be somehow connected? The > hardware in question is 82541EI based: >=20 > em1@pci0:7:8:0: class=3D0x020000 card=3D0x016d1028 chip=3D0x10768086 > rev=3D0x05 > hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82541EI Gigabit Ethernet Controller' > class =3D network > subclass =3D ethernet >=20 > Thanks in advance! >=20 > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.12 (FreeBSD) >=20 > iEYEARECAAYFAkp3PQkACgkQi+vbBBjt66A2CQCgt+8prSPRDKdOb61gdfj1zpcF > q28An1/UXuo0bcEi4nwlUpYuqD8hR5Lo > =3D56SA > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"