From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsa@cumulusnetworks.com>,
Hajime Tazaki <thehajime@gmail.com>,
lucien.xin@gmail.com,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Subject: [PATCH net 0/2] ipv6: fix sticky pktinfo behaviour
Date: Wed, 27 Jan 2016 14:45:57 +0100 [thread overview]
Message-ID: <cover.1453830778.git.pabeni@redhat.com> (raw)
Currently:
ip addr add dev eth0 2001:0010::1/64
ip addr add dev eth1 2001:0020::1/64
ping6 -I eth0 2001:0020::2
do not leads to the expected results, i.e. eth1 is used as the
egress interface.
This is due to two related issues in handling sticky pktinfo,
used by ping6 to enforce the device binding:
- ip6_dst_lookup_flow()/ip6_dst_lookup_tail() do not really enforce
flowi6_oif match
- ipv6 udp connect() just ignore flowi6_oif
These patches address each issue individually.
Paolo Abeni (2):
ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
ipv6/udp: use sticky pktinfo egress ifindex on connect()
include/net/ip6_route.h | 2 ++
net/ipv6/datagram.c | 3 +++
net/ipv6/ip6_output.c | 6 +++++-
net/ipv6/route.c | 12 +++++++++---
4 files changed, 19 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-01-27 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:45 Paolo Abeni [this message]
2016-01-27 13:45 ` [PATCH net 1/2] ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail() Paolo Abeni
2016-01-27 18:38 ` Hannes Frederic Sowa
2016-01-28 12:27 ` Paolo Abeni
2016-01-28 13:02 ` Hannes Frederic Sowa
2016-01-28 14:59 ` David Ahern
2016-01-28 17:04 ` Paolo Abeni
2016-01-27 13:45 ` [PATCH net 2/2] ipv6/udp: use sticky pktinfo egress ifindex on connect() Paolo Abeni
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=cover.1453830778.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=thehajime@gmail.com \
/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).