From: Daniel Borkmann <dborkman@redhat.com>
To: netdev@vger.kernel.org
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCH net-next] ipv6: rearm router solicitaion timer when setting new tokenized address
Date: Wed, 26 Jun 2013 19:16:45 +0200 [thread overview]
Message-ID: <51CB21FD.3060602@redhat.com> (raw)
In-Reply-To: <20130626014149.GB20081@order.stressinduktion.org>
On 06/26/2013 03:41 AM, Hannes Frederic Sowa wrote:
> When a new tokenized address gets installed we send out just one
> router solicition. We should send out `rtr_solicits' in case one router
> advertisment got lost.
>
> So, rearm the timer as we do in addrconf_dad_complete.
>
> Cc: Daniel Borkmann <dborkman@redhat.com>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Acked-by: Daniel Borkmann <dborkman@redhat.com>
next prev parent reply other threads:[~2013-06-26 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 1:41 [PATCH net-next] ipv6: rearm router solicitaion timer when setting new tokenized address Hannes Frederic Sowa
2013-06-26 17:16 ` Daniel Borkmann [this message]
2013-06-26 22:23 ` 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=51CB21FD.3060602@redhat.com \
--to=dborkman@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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).