Subject: Re: nd6_lookup: failed to add route... noise with freenet6 tunnel
To: Jun-ichiro itojun Hagino <>
From: Robert Elz <kre@munnari.OZ.AU>
List: tech-net
Date: 08/15/2001 03:47:56
    Date:        Wed, 15 Aug 2001 01:47:05 +0900
    From:        Jun-ichiro itojun Hagino <>
    Message-ID:  <>

  | [Quoting Frederick Bruckman]
  | >I've obtained a point-to-point tunnel from, built "tspc",
  | >and it mostly works fine.

Works fine for me, though the netbsd template script wasn't really
adequate (badly confused prefix allocation and subnet numbering).
This probably only matters if you're getting a /48 from freenet6
and using the tunnel to provide routing to a lan (or group of lans).

  | 	don't configure like above.

That's the way the tspc template scripts set things up.

  | 	don't use prefixlen 64 with both src/dst specified.  this is the
  | 	reason for the kernel message "nd6_lookup: blah".

I do, on that tunnel, and I have no problems like that...
(and I think I saw your name as the contributor of that script).

gif1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
        tunnel inet -->
        inet6 fe80::290:27ff:fe24:c8f4%gif1 -> :: prefixlen 64 scopeid 0x5
        inet6 3ffe:b80:2:1a2::2 -> 3ffe:b80:2:1a2::1 prefixlen 64

That's the freenet6 tunnel.   Works fine.

What I do on my manually configured tunnel is ...

gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1480
        tunnel inet -->
        inet6 fe80::290:27ff:fe24:c8f4%gif0 -> :: prefixlen 64 scopeid 0x4
        inet6 3ffe:8001:2:ffff::102:1 -> :: prefixlen 127

which also works fine.   This is on (currently) 1.5W (haven't recompiled
for a few weeks).