From: Yan Zheng <yanzheng@21cn.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH]behavior of ip6_route_input() for link local address.
Date: Thu, 20 Oct 2005 12:51:34 +0800 [thread overview]
Message-ID: <43572256.40101@21cn.com> (raw)
Hi
I find that linux will reply echo request destined to an address which belongs to an interface other than the one from which the request received.
This behavior doesn't make sense for link local address.
Index: net/ipv6/route.c
===================================================================
--- linux-2.6.14-rc4-git6/net/ipv6/route.c 2005-10-20 12:02:49.000000000 +0800
+++ linux/net/ipv6/route.c 2005-10-20 12:21:03.000000000 +0800
@@ -483,7 +483,7 @@
goto out;
}
- rt = rt6_device_match(rt, skb->dev->ifindex, 0);
+ rt = rt6_device_match(rt, skb->dev->ifindex, strict);
BACKTRACK();
if (!rt->rt6i_nexthop && !(rt->rt6i_flags & RTF_NONEXTHOP)) {
next reply other threads:[~2005-10-20 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 4:51 Yan Zheng [this message]
2005-10-21 8:27 ` [PATCH]behavior of ip6_route_input() for link local address YOSHIFUJI Hideaki / 吉藤英明
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=43572256.40101@21cn.com \
--to=yanzheng@21cn.com \
--cc=linux-kernel@vger.kernel.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).