From owner-freebsd-net Tue Jan 16 9: 5: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 224DA37B400; Tue, 16 Jan 2001 09:04:47 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id CAA14577; Wed, 17 Jan 2001 02:04:26 +0900 (JST) To: horape@tinuviel.compendium.net.ar Cc: Kris Kennaway , freebsd-net@FreeBSD.ORG In-reply-to: horape's message of Tue, 16 Jan 2001 02:58:03 -0300. <20010116025802.A9040@tinuviel.compendium.net.ar> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Problem with gif tunnel: nd6_lookup: failed to add route for a neighbor From: itojun@iijlab.net Date: Wed, 17 Jan 2001 02:04:26 +0900 Message-ID: <14575.979664666@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > Jan 16 02:34:05 ipv6-gw /kernel: nd6_lookup: failed to add route for a = >neighbor(3ffe:2900:000b:000d::0001), errno=3D17 >> >=20 >> > each time i use such tunnel >> >=20 >> > I've looked at some search engines and know it's a common problem but no >> > known solution (i'm tempted to recompile commenting out the log call) >>=20 >> 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. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message