From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 8 19:00:37 2006 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 550E016A422; Wed, 8 Mar 2006 19:00:37 +0000 (GMT) (envelope-from support@freenet6.net) Received: from ex.hexago.com (ex.hexago.com [206.162.147.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5F9643D45; Wed, 8 Mar 2006 19:00:36 +0000 (GMT) (envelope-from support@freenet6.net) Received: from localhost (retro.hexago.com [IPv6:2001:5c0:0:1::5]) by ex.hexago.com ( hexago/8.13.4) with ESMTP id k28Iwx5k000765; Wed, 8 Mar 2006 13:59:00 -0500 (EST) (envelope-from support@freenet6.net) Date: Wed, 08 Mar 2006 14:00:29 -0500 From: Freenet6 Support To: Paul Blazejowski , Freenet6 Support Message-ID: <2F50B25AB5B6286CA88DA37E@techno.hexago.com> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Tilman Linneweh , diffie@blazebox.homeip.net, freebsd-bugs@FreeBSD.org Subject: Re: misc/93220: nd6_lookup: failed to add route for a neighbor X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 19:00:37 -0000 --On Wednesday, March 08, 2006 1:04 PM -0500 Paul Blazejowski 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 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@freenet6.net ------------------------------------------------ http://www.freenet6.net Free IPv6 connectivity, powered by the Hexago Migration Broker (tm) http://www.hexago.com ------------------------------------------------