From: Pekka Savola <pekkas@netcore.fi>
To: Mika Liljeberg <mika.liljeberg@welho.com>
Cc: Andre Tomt <andre@tomt.net>, <linux-kernel@vger.kernel.org>,
<netdev@oss.sgi.com>
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
Date: Fri, 11 Jul 2003 14:48:54 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307111446250.27865-100000@netcore.fi> (raw)
In-Reply-To: <1057923396.893.16.camel@hades>
On 11 Jul 2003, Mika Liljeberg wrote:
> Here's a valid use for subnet router anycase that isn't working.
> Somebody asked me how to set up 6to4, so I did a little testing.
>
> Doesn't work:
>
> hades:~# ip route add ::/0 via 2002:c058:6301::
> RTNETLINK answers: Invalid argument
>
> Works:
>
> hades:~# ip route add ::/0 via 2002:c058:6301::1
>
> Unfortunately the first form is what I need:
>
> hades:~# host -t AAAA 6to4.ipv6.funet.fi
> 6to4.ipv6.funet.fi has AAAA address 2001:708:0:1::624
> 6to4.ipv6.funet.fi has AAAA address 2002:c058:6301::
I think that in this particular case, if should have configured your
interface address with 2002:v4:addr::/16, of which subnet anycast router
address would be 2002::.
> So apparently there really is an inappropriate subnet router anycast
> sanity check. Please fix this!
This *may* be caused by another issue too: nexthop's must be given in the
compatible "::192.88.99.1" format, not 2002:xxxx :-(
I sent a patch on over a year or so ago, but it didn't gain that much
enthusiasm..
--
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-11 11:34 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
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 [this message]
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.0307111446250.27865-100000@netcore.fi \
--to=pekkas@netcore.fi \
--cc=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.liljeberg@welho.com \
--cc=netdev@oss.sgi.com \
/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).