[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 03645) Re: How to retrieve kernel's IPv6 routing cache table?
- To: pb@xxxxxxxxxxxx
- Subject: (usagi-users 03645) Re: How to retrieve kernel's IPv6 routing cache table?
- From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Date: Thu, 30 Mar 2006 23:58:38 +0900 (JST)
- Cc: netdev@xxxxxxxxxxxxxxx
- In-reply-to: <442BED92.4030007@bieringer.de>
- Organization: USAGI/WIDE Project
- Organization: USAGI/WIDE Project
- References: <442BED92.4030007@bieringer.de>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Resent-date: Thu, 30 Mar 2006 23:59:25 +0900 (JST)
- Resent-from: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Resent-message-id: <20060330.235925.02236800.yoshfuji@linux-ipv6.org>
- Resent-to: usagi-users@xxxxxxxxxxxxxx
Hello.
In article <442BED92.4030007@xxxxxxxxxxxx> (at Thu, 30 Mar 2006 16:39:14 +0200), Peter Bieringer <pb@xxxxxxxxxxxx> 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