public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
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.] building testbed for batman-adv and expected performance/throughput
Date: Wed, 2 Jun 2010 07:31:44 +0200	[thread overview]
Message-ID: <20100602053144.GB31330@lunn.ch> (raw)
In-Reply-To: <4C058626.4060108@interia.pl>

On Wed, Jun 02, 2010 at 12:13:58AM +0200, Krzysztof Urbas wrote:
> Hello,
> I am writing my master thesis about performance of BATMAN routing
> protocol and so I build a simple testbed consisting of 4 nodes and
> configured them to run batman-adv. But results of my tests are quite
> strange and I don't really know what should I expected.

Hi Krysztof

What is your definition of "performance of BATMAN routing protocol"?
What are you interested in?

Building a testbed using real hardware is actually very hard. There is
so much radio pollution in the 2.4GHz band you can never have
reproducibility and your bandwidths measurements are mostly
meaningless. The question is, do you want real world measurements,
where pollution is normal, or do you want ideal world measurements?

A few suggestions:

Move to 5GHz. There is less pollution, but still some, so your
reproducibility will improve.

Throw away the antennas and use coax cables, splitters and
attenuators. By moving to a wired system, you should be able to block
much of the interference from pollution. It will not be perfect, since
the devices themselves are generally not very well shielded, but it
will make it better. It also gives you better control of the mesh,
since you can determine the attenuation between nodes.

To make your test setup easier to use, add more linux boxes. Each
wireless node should be connected to a linux box as source/sink of the
traffic. Using a second interface network these boxes together on a
separate network. You can then manage these boxes remotely using the
management network, performing tests over the mesh network.

Throw away the hardware and use a software only solution. People have
used qemu to emulate nodes and bridged them together. Take a look at:

http://www.open-mesh.org/wiki/Emulation

	Andrew

  reply	other threads:[~2010-06-02  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 22:13 [B.A.T.M.A.N.] building testbed for batman-adv and expected performance/throughput Krzysztof Urbas
2010-06-02  5:31 ` Andrew Lunn [this message]
2010-06-02  9:05 ` Daniel Seither

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=20100602053144.GB31330@lunn.ch \
    --to=andrew@lunn.ch \
    --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