From: Phil Sutter <phil@nwl.cc>
To: netdev@vger.kernel.org
Cc: "YOSHIFUJI Hideaki/吉藤英明" <hideaki.yoshifuji@miraclelinux.com>
Subject: Sending IPv6 packets broken in net-next
Date: Thu, 16 Jul 2015 00:20:46 +0200 [thread overview]
Message-ID: <20150715222046.GE14670@orbit.nwl.cc> (raw)
Hi,
Commit 9131f3d ("ipv6: Do not iterate over all interfaces when finding
source address on specific interface") breaks local output of IPv6
packets. Here is a simple reproducer:
---- 8< -----
ip link add eth6 type veth peer name eth7
ip netns add test
ip link set eth7 netns test
ip netns exec test ip link set eth7 up
ip netns exec test ip a a feed:babe::1/64 dev eth7
ip link set eth6 up
ip a a feed:babe::2/64 dev eth6
ping6 feed:babe::1
---- 8< -----
Output from 'tcpdump -npi eth6':
| 00:08:24.214584 IP6 :: > feed:babe::1: ICMP6, echo request, seq 22, length 64
| 00:08:25.214540 IP6 :: > feed:babe::1: ICMP6, echo request, seq 23, length 64
Cheers, Phil
next reply other threads:[~2015-07-15 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 22:20 Phil Sutter [this message]
2015-07-16 7:47 ` Sending IPv6 packets broken in net-next Phil Sutter
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=20150715222046.GE14670@orbit.nwl.cc \
--to=phil@nwl.cc \
--cc=hideaki.yoshifuji@miraclelinux.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).