From owner-freebsd-net@FreeBSD.ORG  Mon May  8 06:58:43 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 85EDA16A4C7;
	Mon,  8 May 2006 06:58:43 +0000 (UTC) (envelope-from ed@hoeg.nl)
Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E298043D6E;
	Mon,  8 May 2006 06:58:42 +0000 (GMT) (envelope-from ed@hoeg.nl)
Received: by palm.hoeg.nl (Postfix, from userid 1000)
	id 1A1F017101; Mon,  8 May 2006 08:58:41 +0200 (CEST)
Date: Mon, 8 May 2006 08:58:41 +0200
From: Ed Schouten <ed@fxq.nl>
To: "Bruce A. Mah" <bmah@freebsd.org>
Message-ID: <20060508065841.GN15353@hoeg.nl>
References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="arYKMy5bKB/hcRo6"
Content-Disposition: inline
In-Reply-To: <445EC341.60406@freebsd.org>
User-Agent: Mutt/1.5.11
Cc: FreeBSD Net <freebsd-net@freebsd.org>
Subject: Re: nd6_lookup prints bogus messages with point to point devices
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 May 2006 06:58:44 -0000


--arYKMy5bKB/hcRo6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Bruce,

* Bruce A. Mah <bmah@freebsd.org> wrote:
> I think that suz@ and ume@ are the people who have worked in this area
> most recently, hopefully one of them will speak up.  You didn't give a
> lot of details...please give (at a minimum) the version of FreeBSD
> you're using and more details about the interface over which you're
> having this problem.
>=20
> I saw this on RELENG_6 sometime after some IPv6 ND changes that were
> merged in late last year.  I have a gif(4) tunnel to my ISP over which I
> do IPv6.  The GIF tunnel was originally configured as a point-to-point
> interface and I got the same messages you mentioned.  My workaround was
> to configure the gif(4) interface as a /127, which was obviously only
> possible because the two interface addresses on each end of the tunnel
> just happened to differ only in their least-significant bits.  (I know
> this isn't the right solution.)

I'm seeing the messages on the machine in Eindhoven (running RELENG_6
=66rom a few days/weeks ago), but they also show up on my HEAD machine at
home. Below is the output of `ifconfig gif0` on my machine at home:

| gif0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
|         tunnel inet 83.181.147.170 --> 193.109.122.244
|         inet6 fe80::202:a5ff:fe58:4927%gif0 prefixlen 64 scopeid 0x7=20
|         inet6 2001:7b8:310::1 --> 2001:7b8:2ff:a4::1 prefixlen 128=20

As far as I know, the latest FreeBSD releases show an error message when
assigning an address with a non-128 prefixlen.

--=20
 Ed Schouten <ed@fxq.nl>
 WWW: http://g-rave.nl/

--arYKMy5bKB/hcRo6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEXuwg52SDGA2eCwURAiqTAJ9mKqasKfUYn4z1IptYKqorsxgecACcClUl
JrWdrEIxkttt/bAlCTFhMzc=
=fHy7
-----END PGP SIGNATURE-----

--arYKMy5bKB/hcRo6--