public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv15 2/4] batman-adv: Add multicast optimization support for bridged setups
Date: Thu, 12 May 2016 23:19:40 +0800	[thread overview]
Message-ID: <7001706.kMMYfbOu1X@voltaire> (raw)
In-Reply-To: <1462898487-9696-3-git-send-email-linus.luessing@c0d3.blue>

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]

On Tuesday, May 10, 2016 18:41:25 Linus Lüssing wrote:
> With this patch we are finally able to support multicast optimizations
> in bridged setups, too. So far, if a bridge was added on top of a
> soft-interface (e.g. bat0) the batman-adv multicast optimizations
> needed to be disabled to avoid packetloss.
> 
> Current Linux bridge implementations and API can now provide us
> with the so far missing information about interested but "remote"
> multicast receivers behind bridge ports.
> 
> The Linux bridge performs the detection of remote participants
> interested in multicast packets with its own and mature so
> called IGMP and MLD snooping code and stores that in its
> database. With the new API provided by the bridge batman-adv can
> now simply hook into this database.
> 
> We then reliably announce the gathered multicast listeners to
> other nodes through the batman-adv translation table.
> 
> Additionally, the Linux bridge provides us with the information about
> whether an IGMP/MLD querier exists. If there is none then we need to
> disable multicast optimizations as we cannot learn about multicast
> listeners on external, bridged-in host then.
> 
> Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
>  compat-include/linux/etherdevice.h |    9 ++
>  compat-include/linux/if_bridge.h   |   68 ++++++++++++++
>  net/batman-adv/multicast.c         |  181
> ++++++++++++++++++++++++++++++++----
> net/batman-adv/types.h             |   13 +++
>  4 files changed, 253 insertions(+), 18 deletions(-)
>  create mode 100644 compat-include/linux/if_bridge.h

Applied in revision 391b59c.

Thanks,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-05-12 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 16:41 [B.A.T.M.A.N.] [PATCHv15 0/4] Multicast optimizations for bridges Linus Lüssing
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 1/4] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2016-05-12 15:14   ` Marek Lindner
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 2/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2016-05-12 15:19   ` Marek Lindner [this message]
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 3/4] batman-adv: Adding logging of mcast flag changes Linus Lüssing
2016-05-12 15:21   ` Marek Lindner
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 4/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2016-05-12 15:22   ` Marek Lindner
2016-05-10 16:50 ` [B.A.T.M.A.N.] [PATCHv15 0/4] Multicast optimizations for bridges Linus Lüssing

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=7001706.kMMYfbOu1X@voltaire \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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