From: chenweilong <chenweilong@huawei.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH] ipv6: don't call addrconf_dst_alloc again when enable lo
Date: Thu, 2 Jan 2014 17:08:15 +0800 [thread overview]
Message-ID: <52C52C7F.6080108@huawei.com> (raw)
In-Reply-To: <20140102083200.GD22494@order.stressinduktion.org>
On 2014/1/2 16:32, Hannes Frederic Sowa wrote:
> On Thu, Jan 02, 2014 at 04:13:40PM +0800, chenweilong wrote:
>> Can you give more explanation about this please?
>
> If you look at the routing table for local addresses (ip -6 route list table
> local), you see that every address which is RTF_LOCAL (and thus passes up the
> packets via ip6_input) has as its device the loopback device.
>
> In case you shutdown loopback you clear all those routes, thus incoming
> packets won't find the corresponding rt6_info which directs the packets to
> passed up the stack.
>
> I guess it was done to satisfy the scoped architecture of IPv6.
>
> Does this help you?
>
>
>
Yes,thanks very much!
next prev parent reply other threads:[~2014-01-02 9:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 3:14 [PATCH] ipv6: don't call addrconf_dst_alloc again when enable lo Gao feng
2013-06-20 6:05 ` David Miller
2013-12-31 3:57 ` Hannes Frederic Sowa
2014-01-02 5:48 ` chenweilong
2014-01-02 6:03 ` Hannes Frederic Sowa
2014-01-02 8:13 ` chenweilong
2014-01-02 8:32 ` Hannes Frederic Sowa
2014-01-02 9:08 ` chenweilong [this message]
2014-01-02 6:54 ` Hannes Frederic Sowa
2014-01-02 7:58 ` chenweilong
2014-01-02 8:23 ` Hannes Frederic Sowa
2014-01-02 9:33 ` chenweilong
2014-01-03 6:53 ` Hannes Frederic Sowa
2014-01-08 7:50 ` Gao feng
2014-01-08 8:05 ` Hannes Frederic Sowa
2014-01-08 8:42 ` Gao feng
2014-01-08 8:55 ` Hannes Frederic Sowa
2014-01-17 2:02 ` chenweilong
2014-01-17 4:09 ` 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=52C52C7F.6080108@huawei.com \
--to=chenweilong@huawei.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 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.