From: Russell King <rmk@arm.linux.org.uk>
To: netdev@oss.sgi.com
Subject: ip -6 route shows incorrect route expiry times
Date: Sun, 30 Jan 2005 16:08:40 +0000 [thread overview]
Message-ID: <20050130160840.C25000@flint.arm.linux.org.uk> (raw)
This looks like a unit conversion error, spotted in Red Hat FC2.
On it's own, it doesn't look like there's anything wrong, until
you look at two copies of the output 10 seconds apart:
rmk@dyn-67:[bk]:<1030> /sbin/ip -6 route; sleep 10; /sbin/ip -6 route
default via fe80::a00:2bff:fe95:1d7b dev eth0 proto kernel metric 1024
expires 169sec mtu 1500 advmss 1440
default via fe80::a00:2bff:fe95:1d7b dev eth0 proto kernel metric 1024
expires 168sec mtu 1500 advmss 1440
It appears that the expiry seconds here are actually in units of
10 seconds. Maybe someone's double-converting kernel Hz to user Hz?
--
Russell King
next reply other threads:[~2005-01-30 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 16:08 Russell King [this message]
2005-01-30 16:29 ` ip -6 route shows incorrect route expiry times YOSHIFUJI Hideaki / 吉藤英明
2005-01-30 16:30 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-31 11:55 ` Ville Nuorvala
2005-01-30 17:09 ` Patrick McHardy
2005-01-31 2:37 ` David S. 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=20050130160840.C25000@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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).