From: Pekka Savola <pekkas@netcore.fi>
To: Meelis Roos <mroos@linux.ee>
Cc: netdev@vger.kernel.org
Subject: Re: ipv6 routing broken in 2.6.17-rc3,4
Date: Mon, 15 May 2006 19:05:39 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605151904110.12081@netcore.fi> (raw)
In-Reply-To: <Pine.SOC.4.61.0605150909510.29527@math.ut.ee>
On Mon, 15 May 2006, Meelis Roos wrote:
> On my home 6to4 gw, ipv6 routing seems to be broken and everything is sent to
> 6to4 tunnel (the default route). It worked with fine for a long time and with
> 2.6.17-rc2-g4d5c34ec and it's broken with vmlinuz-2.6.17-rc3-g3cd73eed and
> 2.6.17-rc4-g9be2f7c3 (yesterdays kernel).
...
> vaarikas:~# ip -6 route
> 2002:5283:297e::/48 dev tun6to4 metric 256 expires 21332659sec mtu 1480
> advmss 1420 hoplimit 4294967295
You're using the wrong prefix length. The right one is /16. Does
that work?
Maybe the 6to4 hack which didn't heed routing table (so either prefix
length was OK) was removed or changed...
--
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:[~2006-05-15 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 6:18 ipv6 routing broken in 2.6.17-rc3,4 Meelis Roos
2006-05-15 16:05 ` Pekka Savola [this message]
2006-05-15 17:30 ` Meelis Roos
2006-05-15 17:38 ` Meelis Roos
2006-05-25 20:17 ` Meelis Roos
2006-05-25 23:24 ` Meelis Roos
2006-05-26 1:40 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <20060526.104245.106225873.yoshfuji@linux-ipv6.org>
2006-05-26 8:35 ` Meelis Roos
2006-05-26 10:08 ` YOSHIFUJI Hideaki / 吉藤英明
2006-05-26 10:44 ` Meelis Roos
2006-05-26 11:01 ` [PATCH] [IPV6] ROUTE: Don't try less preferred routes for on-link routes YOSHIFUJI Hideaki / 吉藤英明
2006-05-26 20:24 ` David Miller
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.64.0605151904110.12081@netcore.fi \
--to=pekkas@netcore.fi \
--cc=mroos@linux.ee \
--cc=netdev@vger.kernel.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