From owner-freebsd-net@FreeBSD.ORG  Mon Feb  8 11:29:26 2010
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 113DC106566B
	for <freebsd-net@freebsd.org>; Mon,  8 Feb 2010 11:29:26 +0000 (UTC)
	(envelope-from siquijorphilips@gmail.com)
Received: from mail-pz0-f194.google.com (mail-pz0-f194.google.com
	[209.85.222.194])
	by mx1.freebsd.org (Postfix) with ESMTP id E23FA8FC18
	for <freebsd-net@freebsd.org>; Mon,  8 Feb 2010 11:29:25 +0000 (UTC)
Received: by pzk32 with SMTP id 32so4208916pzk.27
	for <freebsd-net@freebsd.org>; Mon, 08 Feb 2010 03:29:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:date:message-id:subject
	:from:to:content-type;
	bh=LtKC4NweRWYmx2GXNo5b6UQHphFfh23U5Ae82jVTJgg=;
	b=eDxGbE/m6zmPB54RB0d3481rl/ouZPLY/3CucpI/JUXHJAL1KzUZgX9LT+0mBQiGfF
	mQ8ZmWaEcZwbtFRRsS+8gISzMSggDm4CZRr3xh7xE7KuOKJ8Xv+7GOhta6bCdjriK2Ld
	Eo97VhmnUJHcdENEtO7kCjS48O/froZVJBIYs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=HSY9M2mwjO1qCtw4RgknxdLmVJj2VHvrxH3GQds5lhCxhh4B/1doaYV0XsY2ALJZY6
	jo77uwq8N5B74D4UMcaQjb86n4o2fcA8CIyBUx78VrPMay6B7Js008pkyfrfN5vD61PQ
	zSe9Rp/FoR2g4yCVEtcfPVjOWmNm5x4Y9YTkA=
MIME-Version: 1.0
Received: by 10.142.1.1 with SMTP id 1mr4178459wfa.108.1265628565469; Mon, 08 
	Feb 2010 03:29:25 -0800 (PST)
Date: Mon, 8 Feb 2010 19:29:25 +0800
Message-ID: <a27b90e41002080329r2e98d940s7390140672a05623@mail.gmail.com>
From: Siquijor Philips <siquijorphilips@gmail.com>
To: freebsd-net@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Intel GigE NIC Issue on IPv6 DAD
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: Mon, 08 Feb 2010 11:29:26 -0000

Hi,

I'm currently doing IPv6 conformance testing with FreeBSD-7.1 RELEASE
however I've encountered DAD timing issue on Intel Gigabit NICs with
em(4) driver. I configure several tweaks on net.inet6.ip6.dad_count
such as 2 seconds, 3 seconds and 4 seconds just to get the specific
DAD timing on each test item. There are 29 test items for a router
category on RFC 4862 (IPv6 Stateless Address Autoconfiguration) and
some items passed on 4 seconds, others passed on 1 second (default DAD
configuration) while others are not consistent (sometimes passed on 4
seconds and if tested again, it will satisfy on 1 second). With FastE
NICs such as Intel 10/100 with fxp(4) driver and Via Rhine 10/100 with
vr(4) driver, these cards just works fine using the default
net.inet6.ip6.dad_count=1 (1 second) without this DAD timing problem.

So my concern is, why does Intel GigE NICs with em(4) driver behave
this way? I have tested 2 Intel GigE NICs with different chipsets,
82541and 82574L and it does the same behavior? Is this a bug or
something?

Regards,
Siquijor