Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp218298imu; Tue, 22 Jan 2019 17:20:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN7vQFsHL1XVADoa/09q8S1DShiNvVZ7VVgr2OiZCf/9Nda3z0Rx8R7B4q1AcjcLE8guRyFh X-Received: by 2002:a63:111c:: with SMTP id g28mr215096pgl.85.1548206405320; Tue, 22 Jan 2019 17:20:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548206405; cv=none; d=google.com; s=arc-20160816; b=Mv7+u+9pCdnD8MWZGQMSgyA9EQ3HSgFdIz5/fKEu/VoxxHSYgzd5PK1QYeaOfl5RGV s+hUW25HpohfGZ/qEf4dKLmbeWGE91Khu/noOxszdTsbcXiljZbHU7AtkbWFPBDyNoE/ Yd/Xx2BLUUOAhGtSVq42AV5rmC4kVhPxFMfPV5IQRuNFf6c10iramC4GXPIkvXp0Dzda nLgYDdWyyps8MHWZ5yAgWMxwq/R/AZpb0hLdQDqCUwJcx2dAIMQ4D8+dfNE3Ij+ed+B3 NiFq/xXgcaD0GWCAMuxhdgVADqQjpjVlNTvVy/vesyEhgrOLM3Tg7PUgTRch568KDy7C preA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=sgPhSpLo46v4S2ffOQCrTOn1XNI0PlKjOd/TJl0X/24=; b=zLOc6KUbriYGpjy1kuAp//rrCBdnsW5TdPrH1zs9ELT0NH6X3g8ZA65e4yNmPnWe3D KKS9ASgGRX93j2E/v3k8Nu75ydbddkw7jqmyVvPsZ2vai2FbM3Pv0GnJ6HI/wSOPa+sG sFlYbuaxMyKaElApyyJ0MgNS5cmdfA0X1ZAIYDwibCC6vn05BMyWczmAawUlhSwW4RHN cx8sRIJf70sj4smoEhxvcNmGA1MSSAoUsooWelqy/PeIwtvweXQHoVf/ARUS+hm3oS9S VVVvc2CPme6m+6pUkmc2kYC+wmD35yF0AZYdtFMCCjWKjLEcBmsuRXO+77hqG02o4XMe z4VA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v69si17575326pgd.284.2019.01.22.17.19.48; Tue, 22 Jan 2019 17:20:05 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726898AbfAWBSg convert rfc822-to-8bit (ORCPT + 99 others); Tue, 22 Jan 2019 20:18:36 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:38738 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726047AbfAWBSg (ORCPT ); Tue, 22 Jan 2019 20:18:36 -0500 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::bf5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 8147F101FC9C1; Tue, 22 Jan 2019 17:18:35 -0800 (PST) Date: Tue, 22 Jan 2019 17:18:32 -0800 (PST) Message-Id: <20190122.171832.1199555290239452595.davem@davemloft.net> To: linus.luessing@c0d3.blue Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next v2 0/4] bridge: implement Multicast Router Discovery (RFC4286) From: David Miller In-Reply-To: <20190121062628.2710-1-linus.luessing@c0d3.blue> References: <20190121062628.2710-1-linus.luessing@c0d3.blue> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 22 Jan 2019 17:18:35 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Linus L?ssing Date: Mon, 21 Jan 2019 07:26:24 +0100 > This patchset adds initial Multicast Router Discovery support to > the Linux bridge (RFC4286). With MRD it is possible to detect multicast > routers and mark bridge ports and forward multicast packets to such routers > accordingly. > > So far, multicast routers are detected via IGMP/MLD queries and PIM > messages in the Linux bridge. As there is only one active, selected > querier at a time RFC4541 ("Considerations for Internet Group Management > Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping > Switches") section 2.1.1.a) recommends snooping Multicast Router > Advertisements as provided by MRD (RFC4286). > > > The first two patches are refactoring some existing code which is reused > for parsing the Multicast Router Advertisements later in the fourth > patch. The third patch lets the bridge join the all-snoopers multicast > address to be able to reliably receive the Multicast Router > Advertisements. ... Series applied, thanks!