From: Simon Wunderlich <sw@simonwunderlich.de>
To: Jake.Harris@zf.com
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] broadcast storms
Date: Mon, 12 Nov 2018 18:13:33 +0100 [thread overview]
Message-ID: <5197276.b4DnEGo6x7@prime> (raw)
In-Reply-To: <B99A1AB9A294834C8DF94185A5E9D18101784D2A0E@NRTV96002.america.zf-world.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hi Jake,
On Monday, November 12, 2018 2:29:07 PM CET Jake.Harris@zf.com wrote:
> My apologies bringing this back but I'm still having trouble with this. Each
> of my 50 nodes sends a 100 byte packet via broadcast every 30 seconds, even
> if coincidently they all transmit it at the same time that's only 5kB of
> data to move, much under the 1MB (default I believe?) bandwidth for
> multicast. Unless there's a large amount of broadcast traffic outside of my
> python program I don't see this being the culprit.
Mhm, this is really not much data ... did you try the multicast as suggested
in an earlier reply?
>
> The storms tend to start when connection to a few nodes gets flakey, so I
> can see the reset protection setting being helpful, how do I set
> BATADV_RESET_PROTECTION_MS? Is this an environment variable or do I set it
> with batctl?
BATADV_RESET_PROTECTION_MS is a define in the batman-adv C-code, so it can't be
set at runtime but only at compile time.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-12 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 13:07 [B.A.T.M.A.N.] broadcast storms Jake.Harris
2018-10-22 14:26 ` Simon Wunderlich
2018-10-22 17:27 ` Jake.Harris
2018-10-22 18:17 ` Simon Wunderlich
2018-11-12 14:29 ` Jake.Harris
2018-11-12 17:13 ` Simon Wunderlich [this message]
2018-11-13 14:55 ` Jake.Harris
2018-11-13 15:26 ` 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=5197276.b4DnEGo6x7@prime \
--to=sw@simonwunderlich.de \
--cc=Jake.Harris@zf.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.