From: Naohiro Ooiwa <nooiwa@miraclelinux.com>
To: netdev@vger.kernel.org, usagi-users@linux-ipv6.org
Cc: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Subject: ping6 is sent out from wrong interface
Date: Fri, 20 Jun 2008 10:42:53 +0900 [thread overview]
Message-ID: <485B0B1D.5000603@miraclelinux.com> (raw)
Hi all,
I configured the IPv6 global address for two interfaces,
and sent the ping with "-I <eth1 address>" to the "ff02::1".
# ifconfig eth0 add 2001:2c0:418:1::2/64
# ifconfig eth1 add 2001:2c0:418:2::2/64
# ping6 -I2001:2c0:418:2::2 ff02::1
# /usr/sbin/tcpdump -ieth1 icmp6 -v -e
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
The ping packets weren't sent from "eth1",
so I captured the packets on the "eth0" by tcpdump.
# /usr/sbin/tcpdump -ieth0 icmp6 -v -e
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:16:53.900751 00:19:d1:19:23:af (oui Unknown) > 33:33:00:00:00:01 (oui Unknown), ethertype IPv6 (0x86dd), length
118: (hlim 64, next-header: ICMPv6 (58), length: 64) 2001:2c0:418:2::2 > ff02::1: ICMP6, echo request, length 64, seq 190
18:16:53.957145 00:1d:09:7a:91:19 (oui Unknown) > 33:33:00:00:00:02 (oui Unknown), ethertype IPv6 (0x86dd), length
70: (hlim 255, next-header: ICMPv6 (58), length: 16) fe80::21d:9ff:fe7a:9119 > ff02::2: [icmp6 sum ok] ICMP6, router
solicitation, length 16
source link-address option (1), length 8 (1): 00:1d:09:7a:91:19
::::::
The ping packets were sent out from "eth0"(00:19:d1:19:23:af),
but IPv6 address was "eth1"(2001:2c0:418:2::2).
Why is interface "eth0". Isn't it bug ?
The following is additional information.
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:19:D1:19:23:AF
inet addr:10.1.0.161 Bcast:10.1.255.255 Mask:255.255.0.0
inet6 addr: 2001:2c0:418:1::1/64 Scope:Global
inet6 addr: fe80::219:d1ff:fe19:23af/64 Scope:Link
::::::
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:10:18:0E:0C:B4
inet addr:172.16.255.200 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: 2001:2c0:418:2::2/64 Scope:Global
inet6 addr: fe80::210:18ff:fe0e:cb4/64 Scope:Link
::::::
# route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:2c0:418:1::/64 * U 256 0 0 eth0
2001:2c0:418:2::/64 * U 256 0 0 eth1
fe80::/64 * U 256 0 0 eth0
fe80::/64 * U 256 0 0 eth1
::::::
2001:2c0:418:1::1/128 * U 0 8 1 lo
2001:2c0:418:2::2/128 * U 0 5 1 lo
::::::
ff00::/8 * U 256 0 0 eth0
ff00::/8 * U 256 0 0 eth1
#
The version used are following:
# uname -r -m
2.6.24.7-92.fc8 i686
# ping6 -V
ping6 utility, iputils-sss20070202
Regards,
Naohiro Ooiwa
next reply other threads:[~2008-06-20 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 1:42 Naohiro Ooiwa [this message]
2008-06-24 20:04 ` ping6 is sent out from wrong interface YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 7:02 Naohiro Ooiwa
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=485B0B1D.5000603@miraclelinux.com \
--to=nooiwa@miraclelinux.com \
--cc=netdev@vger.kernel.org \
--cc=usagi-users@linux-ipv6.org \
--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 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).