| Message ID | 20181221151511.14923-1-linus.luessing@c0d3.blue (mailing list archive) |
|---|---|
| Headers |
Return-Path: <b.a.t.m.a.n-bounces@lists.open-mesh.org> X-Original-To: patchwork@open-mesh.org Delivered-To: patchwork@open-mesh.org Received: from open-mesh.org (localhost [IPv6:::1]) by open-mesh.org (Postfix) with ESMTP id 886218084C; Fri, 21 Dec 2018 16:22:37 +0100 (CET) Authentication-Results: open-mesh.org; dkim=fail reason="key not found in DNS" (0-bit key; unprotected) header.d=c0d3.blue header.i=@c0d3.blue header.b="s388RoDa"; dkim-atps=neutral Received-SPF: None (mailfrom) identity=mailfrom; client-ip=2a01:4f8:171:314c::100:a1; helo=mail.aperture-lab.de; envelope-from=linus.luessing@c0d3.blue; receiver=<UNKNOWN> X-Greylist: delayed 429 seconds by postgrey-1.36 at open-mesh.org; Fri, 21 Dec 2018 16:22:32 CET Received: from mail.aperture-lab.de (mail.aperture-lab.de [IPv6:2a01:4f8:171:314c::100:a1]) by open-mesh.org (Postfix) with ESMTPS id DD5F38084C for <b.a.t.m.a.n@lists.open-mesh.org>; Fri, 21 Dec 2018 16:22:32 +0100 (CET) From: =?utf-8?q?Linus_L=C3=BCssing?= <linus.luessing@c0d3.blue> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1545405322; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=lTRJUL0Yahq7JN1bW0uPxHC2MDoSg3ibls3Avb5GR/M=; b=s388RoDaer9X9snNErQYSgRYEE3Cqz6AwiN/eWp1+DF6xTfx/xnavfbF7FiZow/4JIbxNY xxzEC7l87k1N3FqTUInpB4eDOQUHBgwGNppm3UBbjD19yJXEgXMZS7Tf/hMwVZUZ9UQQSN B2Xq12Qvu5w7bh11BE7+MK0+01eM6+894dE1KaDhm6UMGmxzRTLpIZTK5vXFVVQlCmeJjo B+Xqb30fa11POH66OAr8YNztSEYOgM9zXRw24is0SFTXBLkfCHWef95MOK3ymxRuA279gf Fiyxwm7f5NYmenxcvjCq5WX/UOEAzBV1iedyBAR2a9oyIlPj9HuEfh2dmDhgsQ== To: netdev@vger.kernel.org Date: Fri, 21 Dec 2018 16:15:07 +0100 Message-Id: <20181221151511.14923-1-linus.luessing@c0d3.blue> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1545405322; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=lTRJUL0Yahq7JN1bW0uPxHC2MDoSg3ibls3Avb5GR/M=; b=jZ8yB4xIk9J17F1YY25e9WUhVljLguSPcudp56TnBfz+5iEmFN44fgB2nmdcu6yQGplhxe PgIU2+D4/3O/Srv+hofLvzWhlyLCPJiSTKcCwDPm51TCv2TkaNfOkA0ozMcVmbipB/w4Q9 7vBpnaTmPyuKZv17G8U68S4ZAOTQ6IAwtg7nW5Soq1G0fbzJ+Mt7QX7LOEGrWzEiLbMSWg 8Gl8S1E/W9xAYm6mVoANjB2qJRBR7/1UvstR2bW3U9sdnEdyFHo6o3JdIYuAXFy6QDnyLS cQsNABn/tJlDedZ8zSByTH9fNES+0jUXG95t246RLYfMBU2sTp55Z3Ze6s9c8w== ARC-Seal: i=1; s=2018; d=c0d3.blue; t=1545405322; a=rsa-sha256; cv=none; b=a0Ynt6pKn8Dl+j6ISQ6+Bvs5Tl0wbV8Eg0RKYb5H0Z1zwT0jT0pt9lkZMIPpjta9+UQS8U QVT8Gn9D4zazyLJciAi6LHCKstUuzquCc8jkRZhBmd4qR3Fc7fHeZwwnyr20SZpy5jPf+S mRQwK0rPqocClTWMYC2BC2MyKH7NTrNex4GFqiQg4Qyi39Lw2xmHOYC2dhbOgzgzKekYwB AGnmmKKxhA/+sTmE6pWyXv4/0JAMrd39eQmo+HQHHCwesVrtlXmZ18t2Wx+sFYsHRTZf3R +AqtBYKt6hedachPP+hv0/L2FfFlfJUv6rTUi06Z9EIPf0/u4nOHD4/gEh/GKA== ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Authentication-Results: ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Subject: [B.A.T.M.A.N.] [PATCH net-next 0/4] bridge: implement Multicast Router Discovery (RFC4286) X-BeenThere: b.a.t.m.a.n@lists.open-mesh.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n.lists.open-mesh.org> List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>, <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe> List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/> List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org> List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help> List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>, <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe> Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@lists.open-mesh.org> Cc: b.a.t.m.a.n@lists.open-mesh.org, Nikolay Aleksandrov <nikolay@cumulusnetworks.com>, Roopa Prabhu <roopa@cumulusnetworks.com>, bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>, "David S . Miller" <davem@davemloft.net> Errors-To: b.a.t.m.a.n-bounces@lists.open-mesh.org Sender: "B.A.T.M.A.N" <b.a.t.m.a.n-bounces@lists.open-mesh.org> |
| Series |
bridge: implement Multicast Router Discovery (RFC4286)
|
|
Message
Linus Lüssing
Dec. 21, 2018, 3:15 p.m. UTC
Hi,
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.
What is not implemented yet from RFC4286 yet:
* Sending Multicast Router Solicitations:
-> RFC4286: "[...] may be sent when [...] an interface is
(re-)initialized [or] MRD is enabled"
* Snooping Multicast Router Terminations:
-> currently this only relies on our own timeouts
* Adjusting timeouts with the values provided in the announcements
Regards, Linus
Comments
On 12/21/18 5:15 PM, Linus Lüssing wrote: > Hi, > > 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. > > > What is not implemented yet from RFC4286 yet: > > * Sending Multicast Router Solicitations: > -> RFC4286: "[...] may be sent when [...] an interface is > (re-)initialized [or] MRD is enabled" > * Snooping Multicast Router Terminations: > -> currently this only relies on our own timeouts > * Adjusting timeouts with the values provided in the announcements > > > Regards, Linus > > > Hi Linus, Nice work, unfortunately net-next is currenty closed. Anyway I'll review the patches in detail after the holidays so if there's anything it can be adjusted for when net-next opens up. Thanks, Nik
From: Linus Lüssing <linus.luessing@c0d3.blue> Date: Fri, 21 Dec 2018 16:15:07 +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. ... The net-next tree is currently closed, please resubmit this when it opens back up again. Thank you.