Date: Sun, 12 Feb 2006 02:44:53 GMT From: Paul <diffie@blazebox.homeip.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/93220: nd6_lookup: failed to add route for a neighbor Message-ID: <200602120244.k1C2ireE029356@www.freebsd.org> Resent-Message-ID: <200602120250.k1C2o3XU029757@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93220 >Category: misc >Synopsis: nd6_lookup: failed to add route for a neighbor >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 12 02:50:03 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Paul >Release: 6.1-PRERELEASE >Organization: >Environment: FreeBSD blazebox.homeip.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sat Feb 11 19:41:19 EST 2006 diffie@blazebox.homeip.net:/usr/obj/usr/src/sys/BLAZEBOX i386 >Description: Using ipv6 tunel freemet6 from ports on any recent RELENG_6 system causes hundreds of nd6_lookup: failed to add route for a neighbor(2001:05c0:8fff:fffe::0d0), errno=17 messages a second. The tunel is not started or it's started too early in boot process: Feb 11 21:18:04 blazebox kernel: Starting freenet6. Feb 11 21:18:04 blazebox kernel: tspc - Tunnel Setup Protocol Client v2.1.1 Feb 11 21:18:04 blazebox kernel: Initializing (use -h for help) Feb 11 21:18:04 blazebox kernel: Feb 11 21:18:04 blazebox tspc: tspMain: tspc - Tunnel Setup Protocol Client v2.1.1 Feb 11 21:18:04 blazebox tspc: tspMain: Initializing (use -h for help) Feb 11 21:18:04 blazebox kernel: Feb 11 21:18:04 blazebox kernel: Error is 1: TSP_ERROR Feb 11 21:18:04 blazebox kernel: TSP session done Feb 11 21:18:04 blazebox tspc: tspMain: Error is 1: TSP_ERROR Feb 11 21:18:04 blazebox kernel: Feb 11 21:18:04 blazebox tspc: tspMain: Error is 1: TSP_ERROR Feb 11 21:18:04 blazebox tspc: tspMain: TSP session done Feb 11 21:18:04 blazebox kernel: Starting named. Feb 11 21:18:04 blazebox named[460]: starting BIND 9.3.2 -c /etc/named.conf -u bind -t /var/named Feb 11 21:18:04 blazebox named[460]: loading configuration from '/etc/named.conf' Feb 11 21:18:04 blazebox named[460]: listening on IPv6 interfaces, port 53 Feb 11 21:18:04 blazebox named[460]: listening on IPv4 interface em0, 192.168.0.1#53 Feb 11 21:18:04 blazebox named[460]: listening on IPv4 interface lo0, 127.0.0.1#53 Feb 11 21:18:04 blazebox named[460]: command channel listening on 0.0.0.0#953 Feb 11 21:18:04 blazebox named[460]: errno2result.c:109: unexpected error: Feb 11 21:18:04 blazebox kernel: Feb 11 21:18:04 blazebox named[460]: errno2result.c:109: unexpected error: Feb 11 21:18:04 blazebox named[460]: unable to convert errno to isc_result: 45: Operation not supported Feb 11 21:18:04 blazebox kernel: Feb 11 21:18:04 blazebox named[460]: unable to convert errno to isc_result: 45: Operation not supported Feb 11 21:18:04 blazebox named[460]: could not open entropy source /dev/random: unexpected error Feb 11 21:18:04 blazebox named[460]: using pre-chroot entropy source /dev/random It might be also released to bind errors (although the proper dev entries do exist in chroot). >How-To-Repeat: Install freenet6 port and add it to /etc/rc.conf upon boot it will not start and when manually started, hundreds of above message about ndlookup will spam logs and dmesg. >Fix: None >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602120244.k1C2ireE029356>