public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Line of Nodes
Date: Wed, 12 Mar 2014 13:53:29 +0100	[thread overview]
Message-ID: <20140312125329.GJ1629@pengutronix.de> (raw)
In-Reply-To: <201403121136.16430.sw@simonwunderlich.de>

On Wed, Mar 12, 2014 at 11:36:16AM +0100, Simon Wunderlich wrote:
> >   Gateway - A1 - A2 - A3 - A4 - A5 - ... - A120
> >   Gateway - A9 - A17 - A1 - A47 - A9 - ... - A6
> > [...]
> > 
> > - What do you think, could B.A.T.M.A.N be a solution?
> 
> Yes, BATMAN could help in this situation - its better than doing it
> statically at least, since batman can decide how many intermediate
> hops to skip.

That's what I hoped.

> > - Could the short distance be a problem?
> 
> well you have interference between the nodes and the typical
> throughput limitations because of the half-duplex nature of WiFi. But
> if you take that into consideration and don't expect the same
> throughput as on a single link, 3-4 meter should be fine.

Do you have any good literature/link recommendation where I could learn
more about the low level WiFi mechanics?

> It also depends on what kind of data you will send (many industrial 
> applications use broadcast, for example).

Broadcast is not necessary, all traffic is generated somewhere on the
line and sent out to the Gateway. The datasets are in the 500 KiB range,
it could be UDP or TCP, not decided yet. But it's definitely unicast.

> > - Is it possible to regulate the transmission power in order to avoid
> >   disturbance?
> 
> There are WiFi driver which allow that, yes.

Can you give me a hint which feature I need to search for in the kernel
drivers?

As the stations will be built from scratch (SoC+RAM+Flash+Wifi-Chipset),
we can chose the right chipsets, as long as it's possible to buy them
somewhere.

> However I'd recommend to keep it as it is and change the broadcast
> rate to something higher (e.g. 18M or more) to force to only use good
> links, even if they are a little shorter.

Ok. I'll setup a bunch of prototype devices in the first place anyway,
so we can try it out then.

Thanks for the infos!

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2014-03-12 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 21:25 [B.A.T.M.A.N.] Line of Nodes Robert Schwebel
2014-03-12 10:36 ` Simon Wunderlich
2014-03-12 12:53   ` Robert Schwebel [this message]
2014-03-12 13:51     ` Simon Wunderlich
2014-03-12 14:25       ` Robert Schwebel
2014-03-12 14:54         ` Andrew Lunn
2014-03-12 18:20           ` Robert Schwebel
2014-03-31 11:06             ` Bruno Antunes
2014-03-31 18:14               ` Robert Schwebel

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=20140312125329.GJ1629@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sw@simonwunderlich.de \
    /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