Date: Sun, 17 Sep 2000 10:56:09 -0700 From: Phil Staub <phils@staub.net> To: freebsd-net@freebsd.org Subject: Re: IPv6 woes Message-ID: <20000917105609.A94367@staub.net> In-Reply-To: <87og1nuk3f.fsf@pooh.honeypot>; from kirk@strauser.com on Sun, Sep 17, 2000 at 10:14:12AM -0500 References: <87og1nuk3f.fsf@pooh.honeypot>
next in thread | previous in thread | raw e-mail | index | archive | help
By any chance are you trying to run this script from a machine behind a NATD firewall? I tried to do this and got exactly the same error message. A note to the freenet6 folks revealed that NATD doesn't yet know how to deal with the tunnelling packets. HTH Phil On Sun, Sep 17, 2000 at 10:14:12AM -0500, Kirk Strauser wrote: > I'm running a FreeBSD 4.1-stable system. I went to > www.freenet6.net to get a v6 address, and selected the > FreeBSD/KAME option. Along with the tunkame.*.pl script, it > sent me: > > Your IPv6 address : 3ffe:b00:c18:1fff:0:0:0:455 > Freenet6 IPv6 address (server side) : 3ffe:b00:c18:1fff:0:0:0:454 > Freenet6 IPv4 address (server side): 206.123.31.102 > Your IPv4 address : 216.224.193.50 > > The script executed without errors. However, while I can ping > the local and remote IPv4 address, and I can ping6 the local > IPv6 address, I can't pin6 the remote end. The only error > message I get, at all, is from /var/log/messages: > > /kernel: nd6_lookup: failed to add route for a > neighbor(3ffe:0b00:0c18:1fff::0454), errno=17 > -- Phil Staub, KE7HC phils@staub.net Unix: because reboots are for hardware upgrades To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000917105609.A94367>