From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: pb@bieringer.de
Cc: netdev@vger.kernel.org
Subject: (usagi-users 03645) Re: How to retrieve kernel's IPv6 routing cache table?
Date: Thu, 30 Mar 2006 23:58:38 +0900 (JST) [thread overview]
Message-ID: <20060330.235838.30940800.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <442BED92.4030007@bieringer.de>
Hello.
In article <442BED92.4030007@bieringer.de> (at Thu, 30 Mar 2006 16:39:14 +0200), Peter Bieringer <pb@bieringer.de> says:
> IPv6:
> # ip -6 route show table cache
> ff02::1 via ff02::1 dev eth0 metric 0
> cache mtu 1280 advmss 1220 metric 10 4294967295
> ff02::1:ffea:7781 via ff02::1:ffea:7781 dev eth0 metric 0
> cache mtu 1280 advmss 1220 metric 10 4294967295
>
> That's all? I would expect similar to IPv4 like:
No surprise, that's all.
> # ip -4 route show table cache
> local 127.0.0.1 from 127.0.0.1 dev lo
> cache <local> mtu 16436 advmss 16396 metric 10 64
:
We don't have "cache" route unless it is link-local, or
you got e.g. "too big" or "redirect", so far.
--yoshfuji
parent reply other threads:[~2006-03-30 14:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <442BED92.4030007@bieringer.de>]
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=20060330.235838.30940800.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=pb@bieringer.de \
--cc=usagi-users@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