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.] FW: using Batman-adv
Date: Fri, 08 May 2015 08:33:43 +0200	[thread overview]
Message-ID: <3376805.a4VXV4btx9@sven-edge> (raw)
In-Reply-To: <4837729.AoYrTN5tco@prime>

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

On Thursday 07 May 2015 19:25:11 Simon Wunderlich wrote:
[....]
> There is another suggestion: You could increase the multicast rate to a high
> value, e.g. 36 MBit/s or even higher. Higher rates only work with good
> signals, and since batman-adv uses broadcasts (which is multicast for
> WiFi), this will have a direct effect on your network.
[...]
> Batman-adv is open source, and so is mac80211 and hopefully the WiFi driver
> you use. However, it'd really suggest to start with tuning the multicast
> rate.
> :)

I definitely agree here. This should tested before trying to hack the TQ
calculation with some own RSSI based submetric.

The mcast_rate trick is currently only shown in an old OpenWrt wiki page [1].
Maybe it should also be mentioned in the main OpenWrt configuration page [2].
I will leave this to the interested reader... or I will change it when I
have some time to confirm it with a current OpenWrt.

Kind regards,
	Sven


[1] http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config-sophisticated
[2] http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config

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

  reply	other threads:[~2015-05-08  6:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 17:00 [B.A.T.M.A.N.] FW: using Batman-adv Joseph Zimmer
2015-05-07 17:25 ` Simon Wunderlich
2015-05-08  6:33   ` Sven Eckelmann [this message]
2015-05-08 16:21     ` Joseph Zimmer
2015-05-07 18:19 ` Sven Eckelmann
2015-05-08 15:49 ` Ray Gibson

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=3376805.a4VXV4btx9@sven-edge \
    --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