[Battlemesh] recommendations for 40Km Link / OpenWRT on ubnt ath9k hw ?
hrogge at gmail.com
Wed Mar 26 06:42:50 CET 2014
Maybe it would be easier to build a "point to point TDMA" module
independent of the wifi stack? Similar to the BATMAN-advanced
implementation just as a "tunnel device" that can run over any kind of
On Wed, Mar 26, 2014 at 2:04 AM, Mitar <mitar at tnode.com> wrote:
> Let me once more call for open TDMA ath9k drivers!
>> El 25/03/14 09:46, Laurent GUERBY escribió:
>>> On Mon, 2014-03-24 at 18:58 -0300, Nicolás Echániz wrote:
>>>> We plan to use OpenWrt everywhere when ath9k gets more stable, so far we
>>>> have had different issues with every release we tested for the past year
>>>> or so.
>>> Did you open bugs for these issues? We'd like to migrate
>>> our ubnt gear from AirOS to OpenWRT so we're really
>>> interested in experiences/bugs/...
>> We reported many that were fixed over time, but then hit new ones.
>> We bumped into things that are quite difficult to reproduce "in the
>> lab", like a radio stopping to receive any packets for no apparent
>> reason. Or a whole adhoc cloud going numb for minutes when one node is
>> reset or powered off.
>> We gave Felix direct access to nodes inb one of our networks so he could
>> see some of these symptoms first hand a while back. This is always an
>> These bugs I'm mentioning were fixed later on but others crawled in.
>> Guido can better comment on the last one he hit (I haven't updated for a
>> while now).
>> I'm currently using a not-current wireless with bugs I know how to work
>> around... but this is not an option for town to town links where a lot
>> of people are depending on stability there.
>> Regarding raw performance, we have the same experience others expressed.
>> OpenWrt on ath9k performs more or less the same as AirOS; more on hidden
>> nodes, TDMA, etc. on next email :)
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
More information about the Battlemesh