Date: Mon, 30 Jun 2008 11:19:54 -0400 (EDT) From: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> To: steve@ibctech.ca (Steve Bertrand) Cc: freebsd-net@freebsd.org, "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> Subject: Re: [freebsd-net] Re: IPV6 problem : nd6_lookup: failed to add route for a neighbor Message-ID: <200806301519.m5UFJsOe072577@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <4868E183.2070504@ibctech.ca>
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. > Possibly because of : http://lists.freebsd.org/pipermail/freebsd-net/2006-May/010718.html http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/93220 which wouldn't apply to me due to my version. > > > 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. > It seems if I just did : ifconfig gif0 inet6 2001:470:7:28::2/64 instead of : ifconfig gif0 inet6 2001:470:7:28::2 2001:470:7:28::1 prefixlen 128 It "got happy". I haven't seen any of the messages yet, and so far no issues I can readily see. Tuc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806301519.m5UFJsOe072577>