Date: Wed, 08 Mar 2006 13:04:27 -0500 From: Paul Blazejowski <paulb@blazebox.homeip.net> To: Freenet6 Support <support@freenet6.net> Cc: Tilman Linneweh <arved@FreeBSD.org>, diffie@blazebox.homeip.net, freebsd-bugs@FreeBSD.org Subject: Re: misc/93220: nd6_lookup: failed to add route for a neighbor Message-ID: <1141841067.9020.15.camel@blaze.homeip.net> In-Reply-To: <CD7C6129C5C483A164726AF2@techno.hexago.com> References: <200602122117.k1CLHxWN008260@freefall.freebsd.org> <1141789857.9035.4.camel@blaze.homeip.net> <CD7C6129C5C483A164726AF2@techno.hexago.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2006-03-08 at 09:21 -0500, Freenet6 Support wrote:
Hello Jean,
>
> 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.
I am sorry but the ifconfig i posted to the bug report obscured the real
ipv6 addresses, here is the output from the ifconfig gif0:
--> ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 68.237.254.104 --> 64.86.88.116
inet6 2001:5c0:8fff:fffe::d61 --> 2001:5c0:8fff:fffe::d60
prefixlen 128
inet6 fe80::220:edff:fe88:e0d7%gif0 prefixlen 64 scopeid 0x8
>
> 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.
I have not installed the freenet6 tspc client manually but rather use
the FreeBSD port from /usr/ports/net/freenet6 and i don't think it has
been recently modified by the port author. Nor my configuration changed
as i've used the tscp client since FreeBSD 5.0. I started seening
problems with tspc not being started on boot about 2 months ago when i
updated to STABLE_6 branch (which has changes to the boot process). This
works on FreeBSD 6.0-RELEASE though.
>
> 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.
>
I think the problem is evident now, these are verbose results from the
boot process, it seems like the freenet6 rc script is started either too
early or the ppp is started too late and then the tspc cannot find the
nameservers defined in tspc.conf and it fails to start on boot. Here are
the verbose entries from the logs:
Mar 8 12:51:38 blazebox kernel: Starting freenet6.
Mar 8 12:51:38 blazebox kernel: tspc - Tunnel Setup Protocol Client
v2.1.1
Mar 8 12:51:38 blazebox kernel: Initializing (use -h for help)
Mar 8 12:51:38 blazebox kernel:
Mar 8 12:51:38 blazebox tspc: tspMain: tspc - Tunnel Setup Protocol
Client v2.1.1
Mar 8 12:51:38 blazebox tspc: tspMain: Initializing (use -h for help)
Mar 8 12:51:38 blazebox kernel: DNS server name ns2.afraid.org is not
resolving.
Mar 8 12:51:38 blazebox kernel: DNS server name ns4.afraid.org is not
resolving.
Mar 8 12:51:38 blazebox kernel: DNS server name ns.blazebox.homeip.net
is not resolving.
Mar 8 12:51:38 blazebox kernel:
Mar 8 12:51:38 blazebox kernel: Error is 1: TSP_ERROR
Mar 8 12:51:38 blazebox kernel: TSP session done
Mar 8 12:51:38 blazebox tspc: tspVerifyConfig: DNS server name
ns2.afraid.org is not resolving.
Mar 8 12:51:38 blazebox kernel: Mar 8 12:51:38 blazebox tspc:
tspVerifyConfig: DNS server name ns2.afraid.org is not resolving.
Mar 8 12:51:38 blazebox tspc: tspVerifyConfig: DNS server name
ns4.afraid.org is not resolving.
Mar 8 12:51:38 blazebox kernel: Mar 8 12:51:38 blazebox tspc:
tspVerifyConfig: DNS server name ns4.afraid.org is not resolving.
Mar 8 12:51:38 blazebox tspc: tspVerifyConfig: DNS server name
ns.blazebox.homeip.net is not resolving.
Mar 8 12:51:38 blazebox kernel: Mar 8 12:51:38 blazebox tspc:
tspVerifyConfig: DNS server name ns.blazebox.homeip.net is not
resolving.
Mar 8 12:51:38 blazebox tspc: tspMain: Error is 1: TSP_ERROR
Mar 8 12:51:38 blazebox kernel: Mar 8 12:51:38 blazebox tspc:
tspMain: Error is 1: TSP_ERROR
Mar 8 12:51:38 blazebox tspc: tspMain: TSP session done
If there's anything else i could do to help in debugging this please let
me know, i hope its not too late to have this fixed for 6.1 release.
> 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
> ------------------------------------------------
>
Best Regards,
Paul B.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1141841067.9020.15.camel>