public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: cmsv <cmsv@wirelesspt.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] Network coding multi-hop bandwidth loss
Date: Sun, 02 Mar 2014 17:39:18 -0500	[thread overview]
Message-ID: <5313B316.701@wirelesspt.net> (raw)
In-Reply-To: <CANHt3YGgN754sR4V2v0jpgMoTSSg0OVmGMOTRQ3zrF8dS5mA_Q@mail.gmail.com>

I just found out /(the hard way) that using network coding (batman-adv
2013.4) that i have a massive, unbelievable bandwidth loss if i have
more than one hop to the destination

I tested this in a real scenario with 11 nodes as well as 3 nodes in a
house with 3 floors and having one per each floor.

Here is the example with 3 nodes

A <------ B -----> C

From node B to iperf reports me 15 mbit
From node B to node C iperf reports me 9 mbit

Then, from node C to node A i get values bellow 1 mbit such as 647kbits
or less.
More than 3 nodes is to forget.

uci set batman-adv.bat0.network_coding=0 disables nc and solved the
problem which brought the network bandwidth to a more realistic and
mathematical acceptable bandwidth level.

Is this finding known by others ?



-- 


Site: http://wirelesspt.net
Mesh: http://tinyurl.com/wirelesspt
Admin: http://wirelesspt.net/wiki/Cmsv
Twitter: http://twitter.com/wirelesspt
Youtube: https://youtube.com/wirelesspt
Facebook: https://www.facebook.com/wirelesspt
Suporte técnico via sms: 91 19 11 798
Donativos/Paypal: http://tinyurl.com/doar-verba
Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk
Email ao abrigo de: https://creativecommons.org/licenses/by-nc-sa/3.0/pt/




       reply	other threads:[~2014-03-02 22:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANHt3YGgN754sR4V2v0jpgMoTSSg0OVmGMOTRQ3zrF8dS5mA_Q@mail.gmail.com>
2014-03-02 22:39 ` cmsv [this message]
2014-03-12 17:16   ` [B.A.T.M.A.N.] Network coding multi-hop bandwidth loss Martin Hundebøll

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=5313B316.701@wirelesspt.net \
    --to=cmsv@wirelesspt.net \
    --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