Date: Wed, 08 Mar 2006 09:21:13 -0500 From: Freenet6 Support <support@freenet6.net> To: Paul Blazejowski <paulb@blazebox.homeip.net>, Tilman Linneweh <arved@FreeBSD.org> Cc: support@freenet6.net, freebsd-bugs@FreeBSD.org, diffie@blazebox.homeip.net Subject: Re: misc/93220: nd6_lookup: failed to add route for a neighbor Message-ID: <CD7C6129C5C483A164726AF2@techno.hexago.com> In-Reply-To: <1141789857.9035.4.camel@blaze.homeip.net> References: <200602122117.k1CLHxWN008260@freefall.freebsd.org> <1141789857.9035.4.camel@blaze.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Tuesday, March 07, 2006 10:50 PM -0500 Paul Blazejowski <paulb@blazebox.homeip.net> wrote: > On Sun, 2006-02-12 at 21:17 +0000, Tilman Linneweh wrote: >> Synopsis: nd6_lookup: failed to add route for a neighbor >> >> State-Changed-From-To: open->feedback >> State-Changed-By: arved >> State-Changed-When: Sun Feb 12 21:16:41 UTC 2006 >> State-Changed-Why: >> Can you post the output of ifconfig? >> >> One common cause of this error is a wrong prefixlen. >> >> (Although i am seeing the same problem with right prefixlens) >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=93220 >> > > Just FYI again, still seeing the errors on todays cvsup build: > > FreeBSD blazebox.homeip.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: > Tue Mar 7 02:23:52 EST 2006 > diffie@blazebox.homeip.net:/usr/obj/usr/src/sys/BLAZEBOX i386 > > I am going to write to hexago's freenet6 support and see if there's > anything that might need to be updated in their client for it to work > with current release and or future 6.1 releases. > > Thanks again, > > Paul B. Hi Paul. One thing seems very weird from your ifconfig, and that may explain some of the problems: gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 tunnel inet 68.23.23.11 --> 64.86.88.11 inet6 2001:5c0:8fff:fffe::d6 --> 2001:5c0:8fff:fffe::d6 The two tunnel endpoints above are the same. It's not that surprising to see a point to point connection fail if it points to itself. According to the server, 2001:5c0:8fff:fffe::d7/128 should be the client endpoint and ::d6 the server. Was the template/linux.sh script modified recently? That may explain why the wrong endpoints are assigned. Otherwise, the only other way to pinpoint the problem would be to manually run the TSP client in verbose mode (tspc -vvv) and send us the log. Regards, Jean-Francois Tremblay Hexago/Freenet6 Support support@freenet6.net ------------------------------------------------ http://www.freenet6.net Free IPv6 connectivity, powered by the Hexago Migration Broker (tm) http://www.hexago.com ------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CD7C6129C5C483A164726AF2>