From: Pekka Savola <pekkas@netcore.fi>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: cat@zip.com.au, <linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
Date: Thu, 10 Jul 2003 19:08:20 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307101906160.18224-100000@netcore.fi> (raw)
In-Reply-To: <20030711.005542.04973601.yoshfuji@linux-ipv6.org>
On Fri, 11 Jul 2003, YOSHIFUJI Hideaki / [iso-2022-jp] ^[$B5HF#1QL@^[(B wrote:
> In article <20030710154302.GE1722@zip.com.au> (at Fri, 11 Jul 2003 01:43:03 +1000), CaT <cat@zip.com.au> says:
>
> > With 2.4.21-pre2 I can get a nice tunnel going over my ppp connection
> > and as such get ipv6 connectivity. I think went to 2.4.21 and then to
> > 2.4.22-pre4 and bringing up the tunnel fails as follows:
> :
> > 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
>
> This is not bug, but rather misconfiguration;
> you cannot use prefix::, which is mandatory subnet routers
> anycast address, as unicast address.
While technically correct, I'm still not sure if this is (pragmatically)
the correct approach. It's OK to set a default route to go to the
subnet routers anycast address (so, setting a route to prefix:: should
not give you EINVAL).
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
next prev parent reply other threads:[~2003-07-10 15:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 15:43 2.4.21+ - IPv6 over IPv4 tunneling b0rked CaT
2003-07-10 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 15:58 ` CaT
2003-07-10 16:08 ` Pekka Savola [this message]
2003-07-10 16:18 ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 16:19 ` Pekka Savola
2003-07-10 19:57 ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Mika Penttilä
2003-07-10 16:27 ` Mika Liljeberg
2003-07-10 23:39 ` CaT
2003-07-11 0:04 ` Mika Liljeberg
2003-07-11 1:49 ` Andre Tomt
2003-07-11 2:03 ` Mika Liljeberg
2003-07-11 2:03 ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 4:51 ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Pekka Savola
2003-07-11 5:20 ` Mika Liljeberg
2003-07-11 5:22 ` Pekka Savola
2003-07-11 5:39 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 8:46 ` Pekka Savola
2003-07-11 9:04 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 9:39 ` Mika Penttilä
2003-07-11 10:03 ` Pekka Savola
2003-07-11 10:47 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:47 ` Pekka Savola
2003-07-11 10:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:59 ` Pekka Savola
2003-07-11 11:03 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 11:04 ` Pekka Savola
2003-07-11 11:36 ` Mika Liljeberg
2003-07-11 11:48 ` Pekka Savola
2003-07-11 12:09 ` Mika Liljeberg
2003-07-11 12:48 ` Mika Penttilä
2003-07-11 13:38 ` Mika Liljeberg
2003-07-11 14:27 ` Mika Penttilä
2003-07-11 14:32 ` Mika Liljeberg
2003-07-11 15:16 ` Mika Penttilä
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0307101906160.18224-100000@netcore.fi \
--to=pekkas@netcore.fi \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).