From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: [PATCH RFCv2 0/4] batman-adv: Unicasting multicast reports to querier-node only
Date: Wed, 1 Apr 2015 10:04:35 +0200 [thread overview]
Message-ID: <1427875479-9240-1-git-send-email-linus.luessing@c0d3.blue> (raw)
The last round of multicast patches send to the batman-adv mailinglist
to add support for the multicast optimizations in bridged scenarios, too,
unfortunately had one major conceptual flaw: It could lead to packet loss.
It's not sufficient to have the unicasting of reports implemented on
bridge-nodes only. Nodes without bridges need to treat reports the same
way.
The issue is described in detail here:
https://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-listener-reports
I'd also be interested in what the netdev/bridge people think about
patches #1 and #2 in particular, therefore including the according mailinglists
now.
Cheers, Linus
Changelog:
v2:
* various bugfixes (now runtime tested, too - should(tm) work)
* added netdev+bridge mailinglists
next reply other threads:[~2015-04-01 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 8:04 Linus Lüssing [this message]
2015-04-01 8:04 ` [PATCH RFCv2 1/4] bridge: multicast: call skb_checksum_{simple_, }validate Linus Lüssing
2015-04-01 8:04 ` [PATCH RFCv2 2/4] net: Export IGMP/MLD message validation code Linus Lüssing
2015-04-01 8:04 ` [PATCH RFCv2 3/4] batman-adv: Forward IGMP/MLD reports to selected querier (only) Linus Lüssing
2015-04-01 17:44 ` David Miller
2015-04-01 8:04 ` [PATCH RFCv2 4/4] batman-adv: Increase BATADV_TVLV_MCAST version number to 2 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=1427875479-9240-1-git-send-email-linus.luessing@c0d3.blue \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).