From mboxrd@z Thu Jan 1 00:00:00 1970 From: CaT Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked Date: Fri, 11 Jul 2003 09:39:31 +1000 Sender: netdev-bounce@oss.sgi.com Message-ID: <20030710233931.GG1722@zip.com.au> References: <20030710154302.GE1722@zip.com.au> <1057854432.3588.2.camel@hades> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: yoshfuji@linux-ipv6.org, linux-kernel@vger.kernel.org, netdev@oss.sgi.com, pekkas@netcore.fi Return-path: To: Mika Liljeberg Content-Disposition: inline In-Reply-To: <1057854432.3588.2.camel@hades> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org On Thu, Jul 10, 2003 at 07:27:13PM +0300, Mika Liljeberg wrote: > On Thu, 2003-07-10 at 18:43, CaT wrote: > > ip tunnel add sit1 mode sit remote 138.25.6.14 > > ip link set sit1 up > > ip addr add 3ffe:8001:000c:ffff::37/127 dev sit1 > > ip route add ::/0 via 3ffe:8001:000c:ffff::36 > > RTNETLINK answers: Invalid argument > > Try this: > > ip route add ::/0 dev sit1 That didn't complain but pings to the ext gw were broken. Noticed the route contained: 3ffe:8001:c:ffff::36/127 via :: dev sit1 proto kernel metric 256 mtu 1480 adv mss 1420 And having remembered /127 being mentioned as bad I changed the interface config to a netmask of /64. Dropped it and brought it up and it all works. There's something fundamental about ipv6 netmasks that I just don't understand... -- "How can I not love the Americans? They helped me with a flat tire the other day," he said. - http://www.toledoblade.com/apps/pbcs.dll/artikkel?SearchID=73139162287496&Avis=TO&Dato=20030624&Kategori=NEWS28&Lopenr=106240111&Ref=AR