From owner-freebsd-net@FreeBSD.ORG Mon Jun 30 13:37:09 2008 Return-Path: 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 5385F106564A for ; Mon, 30 Jun 2008 13:37:09 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id E123A8FC20 for ; Mon, 30 Jun 2008 13:37:08 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 20933 invoked by uid 89); 30 Jun 2008 13:38:41 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 30 Jun 2008 13:38:41 -0000 Message-ID: <4868E183.2070504@ibctech.ca> Date: Mon, 30 Jun 2008 09:37:07 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Tuc at T-B-O-H.NET" References: <200806270430.m5R4U5Ib025336@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200806270430.m5R4U5Ib025336@himinbjorg.tucs-beachin-obx-house.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: IPV6 problem : nd6_lookup: failed to add route for a neighbor X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 13:37:09 -0000 Tuc at T-B-O-H.NET wrote: > But once I brought it all up, I got : > > kernel: nd6_lookup: failed to add route for a neighbor(2001:0470:0007:0028::0001), errno=17 With your exact configuration between two 7.0 boxes, I see no indication of this error whatsoever, with the /128 prefix. > The tunnel came up, was passing traffic, but those messages were > getting out of hand. I tried a prefixlen of 64, and I got: > > ifconfig: ioctl (SIOCAIFADDR): Invalid argument When I attempted to recreate the tunnel with any prefix length other than 128, the same ifconfig error appeared as above. It appears as though when creating a gif tunnel, the only IPv6 prefix length that is valid as far as ifconfig is concerned is /128 even though the link's prefix is /64 even in 7. Steve