public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv11 0/4] Multicast optimizations for bridges
Date: Thu, 10 Mar 2016 19:54:50 +0100	[thread overview]
Message-ID: <1890819.Y64XMdRy2X@bentobox> (raw)
In-Reply-To: <1444205214-5307-1-git-send-email-linus.luessing@c0d3.blue>

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

On Wednesday 07 October 2015 10:06:50 Linus Lüssing wrote:
> This patchset enables the usage of the batman-adv multicast optimizations
> for scenarios involving bridges on top of e.g. bat0, too.
> 
> The first one alters the forwarding behaviour for IGMP and MLD reports
> which is a prerequisite before enabling multicast optimizations in
> bridged setups. It also increases the MCAST TVLV version number to 2.
> More on the issue of insufficient report handling with the v1
> MCAST TVLV can be found here:
> 
> http://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-listener-reports
> 
> The second patch finally enables the multicast optimizations for
> bridged setups.
> 
> Along come two more patches adding according debugging facilities
> to make it possible for the user to check why the multicast
> optimizations might not work ideally to give hints about
> what they might change about their topology.
> 
> 
> This patchset can be found in the current linus/multicast-bridge
> branch.


It looks like these patches don't apply anymore. Can you please resent it
or mark it correctly in patchwork [1,2,3,4].

Thanks,
        Sven

[1] https://patchwork.open-mesh.org/patch/4699/
[2] https://patchwork.open-mesh.org/patch/4729/
[3] https://patchwork.open-mesh.org/patch/4717/
[4] https://patchwork.open-mesh.org/patch/4723/

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

      parent reply	other threads:[~2016-03-10 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  8:06 [B.A.T.M.A.N.] [PATCHv11 0/4] Multicast optimizations for bridges Linus Lüssing
2015-10-07  8:06 ` [B.A.T.M.A.N.] [PATCHv11 1/4] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2015-10-07  8:06 ` [B.A.T.M.A.N.] [PATCHv11 2/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2015-10-07  8:06 ` [B.A.T.M.A.N.] [PATCHv11 3/4] batman-adv: Adding logging of mcast flag changes Linus Lüssing
2015-10-07  8:06 ` [B.A.T.M.A.N.] [PATCHv11 4/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2016-03-10 18:54 ` Sven Eckelmann [this message]

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=1890819.Y64XMdRy2X@bentobox \
    --to=sven@narfation.org \
    --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