From: Meelis Roos <mroos@linux.ee>
To: Pekka Savola <pekkas@netcore.fi>
Cc: netdev@vger.kernel.org
Subject: Re: ipv6 routing broken in 2.6.17-rc3,4
Date: Mon, 15 May 2006 20:38:57 +0300 (EEST) [thread overview]
Message-ID: <Pine.SOC.4.61.0605152035590.10949@math.ut.ee> (raw)
In-Reply-To: <Pine.LNX.4.64.0605151904110.12081@netcore.fi>
>> 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?
Changed tun6to4 to 2002::/16, still the same (packets for eth0 and the
unreachable destination still go to tun6to4).
# ip -6 route
::/96 via :: dev tun6to4 metric 256 expires 21334342sec mtu 1480 advmss 1420 hoplimit 4294967295
unreachable 2001:7a8:1:5::14 dev lo metric 1024 expires 21334363sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
2002:5283:2811:2::/64 dev eth0 metric 256 expires 21334342sec mtu 1500 advmss 1440 hoplimit 4294967295
2002::/16 dev tun6to4 metric 256 expires 21334342sec mtu 1480 advmss 1420 hoplimit 4294967295
2000::/3 via ::192.88.99.1 dev tun6to4 metric 1 expires 21334342sec mtu 1480 advmss 1420 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21332676sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1 metric 256 expires 21334336sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev tun6to4 metric 256 expires 21334342sec mtu 1480 advmss 1420 hoplimit 4294967295
ff00::/8 dev eth1 metric 256 expires 21334336sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev tun6to4 metric 256 expires 21334342sec mtu 1480 advmss 1420 hoplimit 4294967295
ff00::/8 dev eth0 metric 256 expires 21332676sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2006-05-15 17:39 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
2006-05-15 17:30 ` Meelis Roos
2006-05-15 17:38 ` Meelis Roos [this message]
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.SOC.4.61.0605152035590.10949@math.ut.ee \
--to=mroos@linux.ee \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
/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