misc/93220: nd6_lookup: failed to add route for a neighbor

[Freenet6 Support]

--On Wednesday, March 08, 2006 1:04 PM -0500 Paul Blazejowski 
<paulb at blazebox.homeip.net> wrote:

> On Wed, 2006-03-08 at 09:21 -0500, Freenet6 Support wrote:
>
> 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
>
> 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: 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.

In order for tspc to work properly, IPv4 connectivity and DNS 
resolution must be functional. As you suggested, the starting order of 
some services may be the cause.

I don't see what else do say at this point. The behavior of the 
Freenet6 client hasn't changed. Was the start script or the order of 
the services changed?

Regards,
Jeff Tremblay
Hexago/Freenet6 Support
support at freenet6.net
------------------------------------------------
http://www.freenet6.net
Free IPv6 connectivity, powered by the Hexago
Migration Broker (tm) http://www.hexago.com
------------------------------------------------