Re: [B.A.T.M.A.N.] Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) .

[Sven Eckelmann <sven@narfation.org>]

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

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]