From: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, pekkas@netcore.fi
Subject: Re: [PATCH 5 of 5] IPv6: temporary address: update the timer for tentative addresses
Date: Tue, 1 Apr 2008 23:53:25 +0200 [thread overview]
Message-ID: <20080401215325.GN475@pirzuine> (raw)
In-Reply-To: <20080328.122558.13389103.yoshfuji@linux-ipv6.org>
On Fri, Mar 28, 2008 at 12:25:58PM +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <4765830d9f3848ef14e6.1206305173@pirzuine> (at Sun, 23 Mar 2008 21:46:13 +0100), Benoit Boissinot <benoit.boissinot@ens-lyon.org> says:
>
> > IPv6: temporary address: update the timer for tentative addresses
> >
> > Even for tentative addresses, we should update the timer,
> > otherwise if the preferred lifetime is too short we will
> > miss the opportunity to regenerate the adress.
>
> Well, but it this ever happens, it implies that the lifetime
> is too short, doesn't it?
> We don't want such temporary address too much.
I do agree. In this case, short means less than ADDR_CHECK_FREQUENCY
(2 minutes), and it might be too aggressive.
In fact, I don't really know what are the consequences of running
with a very short regen for temporary addresses (let's say for example,
1 minutes preferred lifetime, and 5 minutes valid lifetime).
But it was really useful for me for testing it, and it fixes a bug
(anyway if you use too short lifetimes you'll hit the max addresses
limit really fast).
regards,
Benoit
ps: I'll resubmit the patches to which you already agreed soon.
--
:wq
next prev parent reply other threads:[~2008-04-01 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 20:46 [PATCH 0 of 5] IPv6: Fix temporary address support Benoit Boissinot
2008-03-23 20:46 ` [PATCH 1 of 5] IPv6: do not wrap around when the lifetime has expired Benoit Boissinot
2008-03-27 18:25 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-27 19:38 ` Benoit Boissinot
2008-03-28 3:06 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-01 22:43 ` Benoit Boissinot
2008-03-23 20:46 ` [PATCH 2 of 5] IPv6: only update the lifetime of the relevant temporary address Benoit Boissinot
2008-03-27 18:31 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-23 20:46 ` [PATCH 3 of 5] IPv6: do not create temporary adresses with too short preferred lifetime Benoit Boissinot
2008-03-27 18:39 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-23 20:46 ` [PATCH 4 of 5] IPv6: fix lifetime calculation on temporary address creation Benoit Boissinot
2008-03-28 3:04 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-01 21:56 ` Benoit Boissinot
2008-04-01 23:41 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-02 0:17 ` Benoit Boissinot
2008-04-02 0:25 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-02 5:56 ` Pekka Savola
2008-03-23 20:46 ` [PATCH 5 of 5] IPv6: temporary address: update the timer for tentative addresses Benoit Boissinot
2008-03-28 3:25 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-01 21:53 ` Benoit Boissinot [this message]
2008-03-27 17:59 ` [PATCH 0 of 5] IPv6: Fix temporary address support Benoit Boissinot
2008-03-27 18:12 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-28 0:32 ` Benoit Boissinot
2008-03-28 3:15 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-01 21:55 ` Benoit Boissinot
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=20080401215325.GN475@pirzuine \
--to=benoit.boissinot@ens-lyon.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@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;
as well as URLs for NNTP newsgroup(s).