From: Ruben Wisniewski <ruben@freifunk-nrw.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Simon Wunderlich <simon@open-mesh.com>, felix@freifunk-nrw.de
Subject: [B.A.T.M.A.N.] batman-adv: increased default hop penalty
Date: Mon, 30 Mar 2015 21:27:26 +0200 [thread overview]
Message-ID: <20150330212726.46ff30c5@i3.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Forwarded private message, on request by Simon.
On Friday 27 March 2015 16:52:14 Ruben Wisniewski wrote:
> Hello Simon,
>
>
> we just updated our mesh, to the batman-adv-version 2014.4. Now your
> patch batman-adv: increase default hop penalty[1] is included.
>
> Since we got very large mesh-networks, we have some troubles with your
> patch, which makes long (needed) pathes unusable, because they TQ drop
> to lower zero.
>
> Else, we got some old and some new batman-adv versions, this change
> overloads the old nodes, because their TQ are better, and similiar
> links over new nodes got ignored.
>
> Else I see no improvement overall, because the usual urban link-wide
> is about 30-50 meteres, and we got parts of the net where we need 4-5
> hops to reach the last node. Your Patch seem to limit these pathes to
> something around 3 hops. So parts of our net are now offline, and the
> speed overall doesn't seem to be improved.
>
> After these experience I like to ask you, if you mind reverting this
> patch again. Else we have to work around with resetting to 15 again on
> boot, which I think is not the prefered solution.
>
>
> [1]
> http://www.open-mesh.org/projects/batman-adv/repository/revisions/7644650bb7
> 66bd4c7b6be5d97e6b1c3ed93a38d7
>
>
> Best regards,
>
>
> Ruben
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 303 bytes --]
next reply other threads:[~2015-03-30 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 19:27 Ruben Wisniewski [this message]
2015-03-31 12:18 ` [B.A.T.M.A.N.] batman-adv: increased default hop penalty Simon Wunderlich
2015-04-19 18:25 ` 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=20150330212726.46ff30c5@i3.local \
--to=ruben@freifunk-nrw.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=felix@freifunk-nrw.de \
--cc=simon@open-mesh.com \
/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.