From: Antonio Quartulli <antonio@meshcoding.com>
To: Tom Sparks <tom_a_sparks@yahoo.com.au>,
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.] batman over wireless bridges
Date: Tue, 11 Mar 2014 23:02:11 +0100 [thread overview]
Message-ID: <531F87E3.603@meshcoding.com> (raw)
In-Reply-To: <1394575062.73102.YahooMailNeo@web142504.mail.bf1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
(Forwarding to the ml. please keep it in the CC)
On 11/03/14 22:57, Tom Sparks wrote:
>
>
>
>
>> On Wednesday, 12 March 2014 7:29 AM, Antonio Quartulli <antonio@meshcoding.com> wrote:
>
>>> Hi Tom,
>>
>>
>> On 11/03/14 13:20, Tom Sparks wrote:
>>>
>>>
>>> I am wondering how well batman works over wireless bridges
>>> like this:
>>>
>>> batR <--> wifiB <--> wifiB <--> batR
>>>
>>>
>>> meanings:
>>> BatR: openwrt router with batman installed
>>> wifiB: wifi bridge
>>
>>
>> What is a wifi bridge?
>
> Basically they are two wireless AP that communicate with each only
>> How is it configured?
> I don't have them yet, I am looking at the bulletM from www.ubnt.com
>
>>
>> batman-adv uses the MAC addresses in the 802.11 header to understand
>> which node is a direct neighbour, therefore the bridge in the middle may
>> screw up this mechanism. It really depends on how the bridge is
>> implemented (it is not a standard component).
>>
>>
>> Cheers,
>>
>> --
>> Antonio Quartulli
>>
>
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-03-11 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394526073.90768.YahooMailNeo@web142501.mail.bf1.yahoo.com>
2014-03-11 12:20 ` [B.A.T.M.A.N.] batman over wireless bridges Tom Sparks
2014-03-11 20:29 ` Antonio Quartulli
[not found] ` <1394575062.73102.YahooMailNeo@web142504.mail.bf1.yahoo.com>
2014-03-11 22:02 ` Antonio Quartulli [this message]
2014-03-11 23:03 ` Linus Lüssing
2014-03-12 5:35 ` Tom Sparks
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=531F87E3.603@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=tom_a_sparks@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.