From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH maint v2] batman-adv: fix TT sync flag inconsistencies
Date: Sat, 29 Jul 2017 10:51:07 +0200 [thread overview]
Message-ID: <20170729085107.GG3700@otheros> (raw)
In-Reply-To: <3105199.cDmPPX3bfG@sven-edge>
On Sat, Jul 29, 2017 at 10:25:37AM +0200, Sven Eckelmann wrote:
> On Donnerstag, 6. Juli 2017 07:02:25 CEST Linus Lüssing wrote:
> > This patch fixes an issue in the translation table code potentially
> > leading to a TT Request + Response storm. The issue may occur for nodes
> > involving BLA and an inconsistent configuration of the batman-adv AP
> > isolation feature. However, since the new multicast optimizations, a
> > single, malformed packet may lead to a mesh-wide, persistent
> > Denial-of-Service, too.
> [...]
> > This patch fixes this issue by storing the flags used in the CRC
> > calculation on a a per TT orig entry basis to be able to respond with
> > the correct, original flags in an intermediate TT Response for one
> > thing. And to be able to correctly unset sync flags once all nodes
> > announcing a sync flag vanish for another.
> >
> > Fixes: fa614fd04692 ("batman-adv: fix tt_global_entries flags update")
> > Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
>
> Simon wanted to have a look at this patch before applying it. But I've already
> queued it up for openwrt-routing [1]. This should hopefully help people which
> want to test it.
Ah, funny, did the same for Gluon a few hours ago :D. So I hope
that we might get some test feedback from there, too.
Regards, Linus
https://github.com/freifunk-gluon/gluon/pull/1199
https://github.com/freifunk-gluon/gluon/pull/1200
next prev parent reply other threads:[~2017-07-29 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 5:02 [B.A.T.M.A.N.] [PATCH maint v2] batman-adv: fix TT sync flag inconsistencies Linus Lüssing
2017-07-24 5:48 ` Antonio Quartulli
2017-07-29 8:25 ` Sven Eckelmann
2017-07-29 8:51 ` Linus Lüssing [this message]
2017-07-31 8:51 ` Simon Wunderlich
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=20170729085107.GG3700@otheros \
--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