From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] net: ipmr: add support for passing full packet on wrong vif Date: Fri, 13 Jul 2018 14:21:27 -0700 (PDT) Message-ID: <20180713.142127.787225854322176465.davem@davemloft.net> References: <20180713091643.22745-1-nikolay@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, sharpd@cumulusnetworks.com To: nikolay@cumulusnetworks.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:36570 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731622AbeGMVhv (ORCPT ); Fri, 13 Jul 2018 17:37:51 -0400 In-Reply-To: <20180713091643.22745-1-nikolay@cumulusnetworks.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Nikolay Aleksandrov Date: Fri, 13 Jul 2018 12:16:43 +0300 > This patch adds support for IGMPMSG_WRVIFWHOLE which is used to pass > full packet and real vif id when the incoming interface is wrong. > While the RP and FHR are setting up state we need to be sending the > registers encapsulated with all the data inside otherwise we lose it. > The RP then decapsulates it and forwards it to the interested parties. > Currently with WRONGVIF we can only be sending empty register packets > and will lose that data. > This behaviour can be enabled by using MRT_PIM with > val == IGMPMSG_WRVIFWHOLE. This doesn't prevent IGMPMSG_WRONGVIF from > happening, it happens in addition to it, also it is controlled by the same > throttling parameters as WRONGVIF (i.e. 1 packet per 3 seconds currently). > Both messages are generated to keep backwards compatibily and avoid > breaking someone who was enabling MRT_PIM with val == 4, since any > positive val is accepted and treated the same. > > Signed-off-by: Nikolay Aleksandrov Applied.