From: johnzeng <johnzeng2013@yahoo.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) .
Date: Wed, 26 Oct 2016 07:19:59 +0800 [thread overview]
Message-ID: <580FE89F.1090808@yahoo.com> (raw)
In-Reply-To: <2155840.zTA8OrSqiX@bentobox>
Hello Sven:
Thanks you for your advisement , and i will start via two Rt2070 at
first , but i will purchase suitable wifi network card or wifi module
recently ,
Whether Atheros (AR54xx、AR91xx、AR92xx、AR93xx及AR95xx) will be
suitable for batman-adv ?
their driver is ath9k .
Have a good day with you
Best Regards
Tiger
于 2016年10月25日 17:45, Sven Eckelmann 写道:
> On Dienstag, 25. Oktober 2016 17:25:50 CEST johnzeng wrote:
>> Hello Dear Sir :
>>
>> Whether Batman-adv need suitable wifi network card (support interface
>> modes ( mesh point ) ) .
> "mesh point" is for 802.11s. You can use 802.11s (mesh point) interfaces
> for batman-adv when you set mesh_fwding to 0. But most people use IBSS
> (adhoc) at the moment for batman-adv. It doesn't really care that much
> about the underlying interface. It just has to be ethernet compatible
> and support some basic features like broadcast.
>
> So you could even run infrastructure mode (AP+Sta) with batman-adv. But
> it doesn't make a lot of sense in most situations :)
>
> The B.A.T.M.A.N. V algorithm implementation has some extra requirements.
> It must be able to get the expected throughput towards a different device
> from cfg80211. You can check if the driver supports this by checking
> `iw dev wlan0 station dump` and searching for "expected throughput:".
> The Mpbs value should represent the reality (and not be complete bogus).
>
> The biggest problems here are driver/hw bugs. Even the ath9k hardware
> (which works quite well) has its fair share of problems.
>
>> there are two wifi network card , and i thought Rt2070 will support
>> Batman-adv .
>>
>> Because Rt2070 will support interface modes ( mesh point ) , and
>> RTL8188CUS can't support interface modes based mesh point .
> Both advertise support for IBSS. So you can (in theory) use adhoc on
> both devices and run batman-adv on top of these adhoc interfaces. But
> you may end up with driver problems (at least I already had problems
> with Realtek and Ralink hardware). Maybe someone else here already
> tested these two chips and tell us more about them.
>
> Kind regards,
> Sven
next prev parent reply other threads:[~2016-10-25 23:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 9:25 Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) johnzeng
2016-10-25 9:45 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-25 23:19 ` johnzeng [this message]
[not found] ` <580FFD64.7020704@yahoo.com>
2016-10-26 6:07 ` Sven Eckelmann
2016-10-26 7:19 ` johnzeng
2016-10-26 8:17 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-26 12:52 ` johnzeng
2016-10-26 13:05 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-26 13:42 ` johnzeng
2016-10-26 14:58 ` Martin Hundebøll
[not found] ` <mailman.170.1477486357.610.b.a.t.m.a.n@lists.open-mesh.org>
2016-10-26 15:09 ` [B.A.T.M.A.N.] " Simon Wunderlich
2016-10-26 7:00 ` Sven Eckelmann
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=580FE89F.1090808@yahoo.com \
--to=johnzeng2013@yahoo.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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 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.