From owner-freebsd-net Wed Jan 24 9:34:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 3086137B404; Wed, 24 Jan 2001 09:34:28 -0800 (PST) Received: from localhost ([3ffe:501:100f:13ff::a]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id CAA06000; Thu, 25 Jan 2001 02:17:56 +0900 (JST) Date: Thu, 25 Jan 2001 02:00:24 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: freebsd-net@FreeBSD.ORG Cc: horape@tinuviel.compendium.net.ar, Kris Kennaway Subject: Re: Problem with gif tunnel: nd6_lookup: failed to add route for a neighbor In-Reply-To: In your message of "Wed, 17 Jan 2001 02:04:26 +0900" <14575.979664666@coconut.itojun.org> References: <20010116025802.A9040@tinuviel.compendium.net.ar> <14575.979664666@coconut.itojun.org> User-Agent: Wanderlust/2.3.0 (Roam) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 20000414(IM141) Lines: 35 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Wed, 17 Jan 2001 02:04:26 +0900, >>>>> itojun@iijlab.net said: >>> Your address prefix length is incorrect..can't remember what the >>> correct value should be off the top of my head, but it's come up >>> before so it should be in the archives upon closer examination. >> It looks like 128 is the "right" prefixlen. Problem is that my upstream >> provider (Sprint) wants to use 64 as prefixlen (IMHO FBSD is ok, but it >> seems to be the common practice to assign /64 to tunnels) > you need to configure like either: > # ifconfig gif0 3ffe:2900:000b:000d::1 3ffe:2900:000b:000d::2 \ > prefixlen 128 alias > # ifconfig gif0 3ffe:2900:000b:000d::1 prefixlen 64 alias > if you specify both your and peer's address, you need to set prefixlen > to 128. if you specify prefixlen to 64, the peer's address is not > necessary (it will get discovered automatically). > actually, the prefix length on p2p interface does not, and should not > really matter. (the separate problem is that there are multiple > interpretation of p2p in the world - major ones are gated > interpretation and cisco interpretation) > we (as KAME) will try to improve the behavior, like non-working ones > get rejected on ifconfig time or such. Just for your information: I've rewritten the KAME-current code using the stricter check. I believe (or hope) the latest code is much better than before. Please see the KAME's CHANGELOG for more details. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message