public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
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.] bridging problem
Date: Wed, 6 Jun 2012 08:53:38 +0200	[thread overview]
Message-ID: <20120606065338.GB12262@ritirata.org> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAPNuGB5hMDtNhUs29egcVLUBAAAAAA==@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

Hello Walter,

On Wed, Jun 06, 2012 at 12:16:07AM +0200, Walter Robert Ditzler wrote:
> so my question is:
> 1) do i need 2 wireless network card for each batman host?

This would probably be the best choice, but it is not always possible. Like in
your case, your box has only one wlan device.
What you can do is to create more VIF. Each wireless device is represented by a
phy interface (phy0 in your case) and on top of it you can create more than one
Virtual Interface (VIF). Actually, when you issued the command:

iw phy phy0 interface add mesh0 type adhoc

you are creating a VAP named mesh0 on top of phy0. What you could do to achieve
your goal (and what we usually d in the same scenario) is to create another VIF
which will be used as AccessPoint interface.

At that point you will have 
- mesh0, that will be put in bat0
- ap0 (or whatever the name you chose)

Now I think you know what to do :-) You can bridge bat0 and ap0!

Here is a link that explains how it works:
http://linuxwireless.org/en/users/Documentation/iw/vif/


Cheers,

> 2) can i connect tot he batman mesh essid to get access the base lan?

You want to use ap0 at this point.


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-06-06  6:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 20:09 [B.A.T.M.A.N.] bridging problem Walter Robert Ditzler
2012-06-05 20:46 ` Sven Eckelmann
2012-06-05 22:16   ` Walter Robert Ditzler
2012-06-06  6:53     ` Antonio Quartulli [this message]
2012-06-06  6:59     ` Sven Eckelmann
2012-06-06 12:26       ` Walter Robert Ditzler
2012-06-06 12:37         ` Sven Eckelmann
2012-06-06 12:59           ` Walter Robert Ditzler
2012-06-06 13:04             ` Wayne Abroue
2012-06-06 13:08             ` Sven Eckelmann
     [not found]               ` <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAJ8P9S1hURlDutIgnj5PzCIBAAAAAA==@gmail.com>
2012-06-06 16:33                 ` Sven Eckelmann
     [not found]               ` <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAPMeAInHZDxMj0Jo5ITXNbIBAAAAAA==@gmail.com>
2012-06-11 14:35                 ` Sven Eckelmann
2012-06-11 15:46                   ` Walter Robert Ditzler

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=20120606065338.GB12262@ritirata.org \
    --to=ordex@autistici.org \
    --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