From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] ipv4: Allow sending multicast packets on specific i/f using VRF socket Date: Tue, 02 Oct 2018 22:31:20 -0700 (PDT) Message-ID: <20181002.223120.2200244969797905737.davem@davemloft.net> References: <20181001084023.32310-1-mmanning@vyatta.att-mail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, rshearma@vyatta.att-mail.com To: mmanning@vyatta.att-mail.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:54636 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726405AbeJCMSJ (ORCPT ); Wed, 3 Oct 2018 08:18:09 -0400 In-Reply-To: <20181001084023.32310-1-mmanning@vyatta.att-mail.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Mike Manning Date: Mon, 1 Oct 2018 09:40:23 +0100 > From: Robert Shearman > > It is useful to be able to use the same socket for listening in a > specific VRF, as for sending multicast packets out of a specific > interface. However, the bound device on the socket currently takes > precedence and results in the packets not being sent. > > Relax the condition on overriding the output interface to use for > sending packets out of UDP, raw and ping sockets to allow multicast > packets to be sent using the specified multicast interface. > > Signed-off-by: Robert Shearman > Signed-off-by: Mike Manning Applied.