From: Ding Tianhong <dingtianhong@huawei.com>
To: "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
Jon Maloy <jon.maloy@ericsson.com>,
Eric Dumazet <edumazet@google.com>,
Netdev <netdev@vger.kernel.org>, <kargig@void.gr>,
<ppandit@redhat.com>
Subject: Re: [PATCH 1/3 v4] ipv6: do not disable temp_address when reaching max_address
Date: Fri, 16 Aug 2013 08:48:44 +0800 [thread overview]
Message-ID: <520D76EC.6000205@huawei.com> (raw)
In-Reply-To: <20130815190754.GB30746@order.stressinduktion.org>
On 2013/8/16 3:07, Hannes Frederic Sowa wrote:
> On Thu, Aug 15, 2013 at 07:36:03PM +0200, Hannes Frederic Sowa wrote:
>> Now we have to check why these addresses don't go out of tentative state.
>
> Just looked at it. flood_router26 just emits pretty high values for
> RetransTime:
>
> 21:05:52.050159 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 192) fe80::c:2a47:1360:1101 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 192
> hop limit 255, Flags [none], pref high, router lifetime 65535s, reachable time 16384000ms, retrans time 1966080ms
> mtu option (5), length 8 (1): 1500
> 0x0000: 0000 0000 05dc
>
> We are completly in spec here. Just DAD needs a lot of time to finish.
>
> Greetings,
>
> Hannes
>
>
Great job, more and more close to the truth, let's find a better way to finish it.
> .
>
next prev parent reply other threads:[~2013-08-16 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 9:06 [PATCH 1/3 v4] ipv6: do not disable temp_address when reaching max_address Ding Tianhong
2013-08-14 10:15 ` Hannes Frederic Sowa
2013-08-15 0:43 ` Ding Tianhong
2013-08-15 1:24 ` Hannes Frederic Sowa
2013-08-15 2:16 ` Ding Tianhong
2013-08-15 17:36 ` Hannes Frederic Sowa
2013-08-15 19:07 ` Hannes Frederic Sowa
2013-08-16 0:48 ` Ding Tianhong [this message]
2013-08-16 11:07 ` Hannes Frederic Sowa
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=520D76EC.6000205@huawei.com \
--to=dingtianhong@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=jon.maloy@ericsson.com \
--cc=kaber@trash.net \
--cc=kargig@void.gr \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=ppandit@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.