From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] RFC: Unicasting multicast reports to querier-node only
Date: Sun, 15 Mar 2015 02:14:05 +0100 [thread overview]
Message-ID: <1426382049-4335-1-git-send-email-linus.luessing@c0d3.blue> (raw)
WARNING: The following patches were only compile-time tested
- you've been warned ;).
The last round of multicast patches 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
These patches are one suggestion to tackle this issue (alternatives
can be found on the wikipage, too). Let me know what you think about
this approach.
Cheers, Linus
next reply other threads:[~2015-03-15 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 1:14 Linus Lüssing [this message]
2015-03-15 1:14 ` [B.A.T.M.A.N.] [PATCH RFC 1/4] bridge: multicast: call skb_checksum_{simple_, }validate Linus Lüssing
2015-03-15 1:14 ` [B.A.T.M.A.N.] [PATCH RFC 2/4] Export IGMP/MLD message validation code Linus Lüssing
2015-03-15 1:14 ` [B.A.T.M.A.N.] [PATCH RFC 3/4] batman-adv: Forward IGMP/MLD reports to selected querier (only) Linus Lüssing
2015-03-15 1:14 ` [B.A.T.M.A.N.] [PATCH RFC 4/4] batman-adv: increase BATADV_TVLV_MCAST version number to 2 Linus Lüssing
2015-03-15 13:48 ` [B.A.T.M.A.N.] RFC: Unicasting multicast reports to querier-node only 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=1426382049-4335-1-git-send-email-linus.luessing@c0d3.blue \
--to=linus.luessing@c0d3.blue \
--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;
as well as URLs for NNTP newsgroup(s).