From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: chenweilong <chenweilong@huawei.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: don't call addrconf_dst_alloc again when enable lo
Date: Thu, 2 Jan 2014 09:32:00 +0100 [thread overview]
Message-ID: <20140102083200.GD22494@order.stressinduktion.org> (raw)
In-Reply-To: <52C51FB4.3000008@huawei.com>
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?
next prev parent reply other threads:[~2014-01-02 8:32 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 [this message]
2014-01-02 9:08 ` chenweilong
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=20140102083200.GD22494@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=chenweilong@huawei.com \
--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).