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: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: devel@lists.open80211s.org,
	The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>,
	Clara Gnos <clara.gnos@googlemail.com>
Subject: Re: [B.A.T.M.A.N.] A case for batman-11s
Date: Thu, 25 Aug 2011 08:47:17 +0200	[thread overview]
Message-ID: <20110825064717.GA28359@lunn.ch> (raw)
In-Reply-To: <CAEFj9860Ozj--PsaFAd1afAZwjapVC5S6JF8Dv0fZD8MkCvqBA@mail.gmail.com>

On Thu, Aug 25, 2011 at 09:36:14AM +0800, Yeoh Chun-Yeow wrote:
> Hi, all,
> 
> Although batman-adv is a layer 2 routing that works across multiple access
> technologies (not so sure about other technologies, because it mainly use
> for WiFi), but it only make senses if we configure the wireless interface
> operating in adhoc or adhocdemo mode. If we configure the wireless interface
> as Infrastructure mode, all the traffic will go to the AP first, even if we
> can direct communicate between the two STAs.
> 
> Correct me if I am wrong.

Ideally, you have BATMAN on the AP as well as the STA. So you never do
STA->AP->STA hops between BATMAN nodes, you only do a STA->AP BATMAN
hop followed by a AP->STA BATMAN hop. Performing two BATMAN hops means
BATMAN knows the transmit quality of each of the two wireless hop, not
the combined transmit quality of the STA->AP->STA path. So BATMAN
running on the AP can then decide if it makes sense to take a
different path.

There is code to enforce this, i.e. blocking STA->AP->STA transfers,
in the development tree and it has been push upstream to be included
in the mainline kernel.

	 Andrew

  parent reply	other threads:[~2011-08-25  6:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 23:30 [B.A.T.M.A.N.] A case for batman-11s Javier Cardona
2011-08-23 10:32 ` Sven Eckelmann
2011-08-23 22:23   ` Javier Cardona
2011-08-24  7:18     ` Andrew Lunn
2011-08-24 18:30       ` Javier Cardona
2011-08-24 22:23         ` Simon Wunderlich
     [not found]         ` <CAEFj9860Ozj--PsaFAd1afAZwjapVC5S6JF8Dv0fZD8MkCvqBA@mail.gmail.com>
2011-08-25  6:47           ` Andrew Lunn [this message]
2011-08-25  7:27         ` Andrew Lunn

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=20110825064717.GA28359@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=clara.gnos@googlemail.com \
    --cc=devel@lists.open80211s.org \
    --cc=yeohchunyeow@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox