Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jun 2008 09:37:07 -0400
From:      Steve Bertrand <steve@ibctech.ca>
To:        "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net>
Cc:        freebsd-net@freebsd.org
Subject:   Re: IPV6 problem : nd6_lookup: failed to add route for a neighbor
Message-ID:  <4868E183.2070504@ibctech.ca>
In-Reply-To: <200806270430.m5R4U5Ib025336@himinbjorg.tucs-beachin-obx-house.com>
References:  <200806270430.m5R4U5Ib025336@himinbjorg.tucs-beachin-obx-house.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4868E183.2070504>