Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) .
Hello Dear Sir :
Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) .
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 .
this is some info via iw list , whether it will be correct understanding ?
Bus 001 Device 005: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter
Supported interface modes: * IBSS * managed * AP * AP/VLAN * WDS * monitor * mesh point
8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Supported interface modes: * IBSS * managed * AP * monitor * P2P-client * P2P-GO
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
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
On Mittwoch, 26. Oktober 2016 07:19:59 CEST johnzeng wrote: [...]
Whether Atheros (AR54xx、AR91xx、AR92xx、AR93xx及AR95xx) will be suitable for batman-adv ?
their driver is ath9k .
[...]
All should work in their PCI(e) version and I think I've used all of them in the past - not sure about AR54xx (which were early draft-n devices). The first three are rather old and they would not be my first choice.
Kind regards, Sven
b.a.t.m.a.n@lists.open-mesh.org
-
johnzeng -
Sven Eckelmann