From: weidong <weid@np.css.fujitsu.com>
To: netdev@vger.kernel.org
Subject: Re: [Patch][IPv6] Fix wrong routing mechanism for Link Local IPv6 packets
Date: Tue, 30 Jan 2007 23:47:34 +0000 (UTC)
Date: Wed, 21 Feb 2007 10:04:47 -0500 [thread overview]
Message-ID: <1172070287.3394.0.camel@LINE> (raw)
In-Reply-To: <001501c7444d$ed731020$ccb1220a@ZhaoleiSOTEC>
Hello, Mr yoshfuji:
Thanks for your reply.
The following is the figure.
|--------------------------------------------|
| |
| Router |
| | |-------|
| |------| |------| | | other |
| | eth0 |--- | eth1 |------|----|network|
| |------| | |------| | |-------|
|------|------|--------------------|---------|
| v |
| fe80::20c:29ff:fe24:fa0a |
| |
| |
| |
| |
| |
| v
| fe80::20c:29ff:fe24:fa14
|
|
|------|------|
| |------| |
| | eth0 |---|--->fe80::200:ff:fe00:100
| |------| |
| |
| Host |
|-------------|
Host eth0: fe80::200:ff:fe00:100
Router eth0: fe80::20c:29ff:fe24:fa0a
Router eth1: fe80::20c:29ff:fe24:fa14
We ping6 from host's eth0 to Router's eth1. Echo Request's src addr =
fe80::200:ff:fe00:100, dst addr = fe80::20c:29ff:fe24:fa14. And Kernel
just send ICMPv6 redirect packet and then forward the Echo Request to
router's eth0. If we run tcpdump on Host eth0, we can receive the ICMPv6
Redirect packet. And if we send NA which advertises
fe80::20c:29ff:fe24:fa14 MAC address(this is very easy for v6eval tool),
we also can receive the forwarded Echo Request(src:fe80::200:ff:fe00:100
dst is fe80::20c:29ff:fe24:fa14).
I dived into the kernel, and found that maybe function rt6_score_route()
has problems. In rt6_score_route(), if rt6_check_dev() return 0, and the
dst ipv6 addr is link local addr, rt6_socre_route() return -1 directly.
I think this is not correct, we should return -1 only if the entry is in
the route cache, and the dst addr is link local addr. Only entries in
cache may select wrong IPv6 Link Local NIC for a link local dst addr.
because they are copied from static IPv6 fib table entries.
> > Hello, Mr yoshfuji
> > Take ping6 for example. Asumming there is a router which has 2 NICs.
> > eth0 on router has ipv6 addr fe80::20c:29ff:fe24:fa0a, eth1 on router has
> > ipv6 addr fe80::20c:29ff:fe24:fa14. Also there is a host connected to
> > router's eth0, and the host's ipv6 addr is fe80::200:ff:fe00:100. We ping6
> :
>
> I still need more precise figure.
>
> Please draw complete box for the 2-3 boxes (pinger, router (and the
> destination)), link(s) and interfaces.
>
> +-------------+
> | Router |
> +---+-----+---+
> eth0| |eth1
> | |
> eth0|
> +---+-+
> |Host1|
> +-----+
>
> Host1 eth0: fe80:....
> Router eth0: fe80:....
> Router eth1: fe80:...
>
> Or, something like that....
>
> I think you may use other tool such as tgif etc.
>
> --yoshfuji
>
next parent reply other threads:[~2007-01-30 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001501c7444d$ed731020$ccb1220a@ZhaoleiSOTEC>
2007-01-30 23:47 ` weidong [this message]
[not found] ` <1172069832.2682.18.camel@LINE>
2007-01-31 1:08 ` [Patch][IPv6] Fix wrong routing mechanism for Link Local IPv6 packets YOSHIFUJI Hideaki / 吉藤英明
2017-05-16 15:37 Michael Ulmer
2017-05-17 15:39 ` David Miller
[not found] <001101c744ec$5ee31720$ccb1220a@ZhaoleiSOTEC>
2007-01-31 4:11 ` weidong
2007-01-31 5:09 ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-31 5:14 ` (usagi-users 03788) " YOSHIFUJI Hideaki / 吉藤英明
2007-01-31 5:42 ` (usagi-users 03789) " YOSHIFUJI Hideaki / 吉藤英明
2007-02-05 0:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-01-30 7:12 weidong
2007-01-30 7:02 (usagi-users 03778) " weidong
2007-01-30 7:24 ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-30 7:55 ` Wei Dong
2007-01-30 8:40 ` 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=1172070287.3394.0.camel@LINE \
--to=weid@np.css.fujitsu.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).