I just set up my tunnel with SixXS a little bit ago, and I've noticed something really strange. First off, it's a static tunnel. In FreeBSD 6.1's dmesg, I get tons of messages like: nd6_lookup: failed to add route for a neighbor(2001:4830:1500:008c::0001), errno=17 2001:4830:1500:8c::1 is my tunnel's end-point on the POP side. My routing tables for IPv6 are as follows: Internet6: Destination Gateway Flags Netif Expire default 2001:4830:1500:8c::1 UGS gif0 ::1 ::1 UH lo0 2001:4830:1500:8c::1 2001:4830:1500:8c::2 UH gif0 2001:4830:1500:8c::2 link#5 UHL lo0 fe80::%vr0/64 link#1 UC vr0 fe80::250:70ff:feb6:12ce%vr0 00:50:70:b6:12:ce UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#3 UHL lo0 fe80::%gif0/64 link#5 UC gif0 fe80::250:70ff:feb6:12ce%gif0 link#5 UHL lo0 ff01:1::/32 link#1 UC vr0 ff01:3::/32 ::1 UC lo0 ff01:5::/32 link#5 UC gif0 ff02::%vr0/32 link#1 UC vr0 ff02::%lo0/32 ::1 UC lo0 ff02::%gif0/32 link#5 UC gif0 From what I can tell, everything should be fine. The tunnel is also up and operational. The only route I've added after creating the gif0 interface is my default route, which was pretty much like: route -n add -inet6 default 2001:4830:1500:8c::1 Any ideas? It seems to be working properly, but the messages are filling up my logs. I googled and saw a few references to this problem, but with no resolution. It didn't seem to happen with my he.net tunnel and a similar setup. Any help could be greatly appreciated. Thanks! :) *UPDATE* This seems to be a bug with the way FreeBSD handles point-to-point tunnels. I've found some other information on the FreeBSD mailing lists that seems to suggest it was fixed in 6.1-prerelease, but, I'm running 6.1-release and still seeing problems. So I'll keep doing research. If anyone happens to have any ideas, though, I'd appreciate it you'd be able to send them my way. :) Thank you.