From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux•com>
To: David Ahern <dsa@cumulusnetworks•com>, Erik Kline <ek@google•com>,
David Miller <davem@davemloft•net>
Cc: hideaki.yoshifuji@miraclelinux•com,
Lorenzo Colitti <lorenzo@google•com>,
netdev <netdev@vger•kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion•org>
Subject: Re: [PATCH net] net: ipv6: Fix ping to link-local addresses.
Date: Wed, 10 Aug 2016 07:44:18 +0900 [thread overview]
Message-ID: <ed271d49-e796-ebaa-2e71-35711710fd49@miraclelinux.com> (raw)
In-Reply-To: <04a393c9-39f8-8d73-3476-928732e5b193@cumulusnetworks.com>
David Ahern wrote:
> On 8/9/16 1:01 AM, Erik Kline wrote:
>> On 9 August 2016 at 14:20, David Miller <davem@davemloft•net> wrote:
>>> From: Lorenzo Colitti <lorenzo@google•com>
>>> Date: Tue, 9 Aug 2016 10:00:25 +0900
>>>
>>>> Note that pretty much every sendmsg codepath allows other data to take
>>>> precedence over sk_bound_dev_if:
>>>>
>>>> - udpv6_sendmsg: if sin6_scope_id specified on a scoped address
>>>> - rawv6_sendmsg: if sin6_scope_id specified on a scoped address
>>>> - l2tp_ip6_sendmsg: if sin6_scope_id specified on a scoped address
>>>> - ip_cmsg_send: if IP_PKTINFO or IPV6_PKTINFO specified
>>>>
>>>> What should I do about those? -EINVAL? Ignore the conflicting data? Leave as is?
>>>
>>> That's a good point, I guess this needs some more thought.
>>
>> I could see a point of view that says when bound_if is in play sending
>> to destinations on/via other interfaces--by any mechanism--should
>> effectively get ENETUNREACH (or something).
>
> VRF uses this capability to send on an enslaved interface. ie., socket is bound to VRF device to limit packets to that L3 domain and then uses PKTINFO to force a packet out a particular interface.
>
We could extend our code to allow enslave devices, maybe.
--
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux•com>
Technical Division, MIRACLE LINUX CORPORATION
next prev parent reply other threads:[~2016-08-09 22:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 7:42 [PATCH net] net: ipv6: Fix ping to link-local addresses Lorenzo Colitti
2016-08-08 14:26 ` Hannes Frederic Sowa
2016-08-08 14:45 ` Lorenzo Colitti
2016-08-08 16:22 ` 吉藤英明
2016-08-08 15:27 ` David Ahern
2016-08-08 16:24 ` Lorenzo Colitti
2016-08-08 16:27 ` David Ahern
2016-08-09 0:40 ` Lorenzo Colitti
2016-08-08 21:35 ` David Miller
2016-08-09 1:00 ` Lorenzo Colitti
2016-08-09 5:20 ` David Miller
2016-08-09 7:01 ` Erik Kline
2016-08-09 8:37 ` YOSHIFUJI Hideaki
2016-08-09 9:36 ` Hannes Frederic Sowa
2016-08-09 11:42 ` Lorenzo Colitti
2016-08-09 13:21 ` David Ahern
2016-08-09 22:44 ` YOSHIFUJI Hideaki [this message]
2016-08-12 15:45 ` Lorenzo Colitti
2016-08-12 16:04 ` David Ahern
2016-08-15 7:39 ` YOSHIFUJI Hideaki
2016-08-16 15:21 ` Lorenzo Colitti
2016-08-16 16:22 ` David Ahern
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=ed271d49-e796-ebaa-2e71-35711710fd49@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsa@cumulusnetworks$(echo .)com \
--cc=ek@google$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=lorenzo@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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