From owner-freebsd-current@FreeBSD.ORG  Tue Feb 24 19:09:00 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B0C1C16A4CE
	for <current@freebsd.org>; Tue, 24 Feb 2004 19:09:00 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [204.152.187.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA7143D2D
	for <current@freebsd.org>; Tue, 24 Feb 2004 19:09:00 -0800 (PST)
	(envelope-from Peter_Losher@isc.org)
Received: from tardis.isc.org (tardis.isc.org
	[IPv6:2001:4f8:3:bb:230:1bff:fe31:a192])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by farside.isc.org (Postfix) with ESMTP id 77CF1A82B
	for <current@freebsd.org>; Wed, 25 Feb 2004 03:09:00 +0000 (UTC)
	(envelope-from Peter_Losher@isc.org)
From: Peter Losher <Peter_Losher@isc.org>
Organization: ISC
To: current@freebsd.org
Date: Tue, 24 Feb 2004 19:09:12 -0800
User-Agent: KMail/1.6
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200402241909.12918.Peter_Losher@isc.org>
Subject: IPv6 awareness after booting...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2004 03:09:00 -0000

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is more of a nag, than anything else, but when bringing up one of our=
=20
production systems running 5.x, after the login prompt appears, any IPv6=20
traffic (ssh, etc.) is blocked for 60-120 seconds while console spits out=20
these messages.

=2D -=3D-
login: nd6_storelladdr: sdl_alen =3D=3D 0
nd6_storelladdr: sdl_alen =3D=3D 0
nd6_storelladdr: sdl_alen =3D=3D 0
nd6_storelladdr: sdl_alen =3D=3D 0
=2D -=3D-

It's mostly harmless, if annoying (after the 120 seconds, IPv6 conections w=
ork=20
fine)  Has anyone else come across this?

=2D -Peter
=2D --=20
Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow"
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAPBHYPtVx9OgEjQgRAk7nAJwOV0HJ7idJQaXBN7k3VYQRq++LEgCcCXXm
UKYzD67RO0bkmPye5m6CSdw=3D
=3DJjEA
=2D----END PGP SIGNATURE-----