[Commotion-discuss] HIgh volume performance

David Banks david.adam.banks at gmail.com
Fri Mar 20 13:19:57 EDT 2015


This has all been extremely helpful thank you all so much.

On Fri, Mar 20, 2015 at 1:02 PM, Adam Longwill <adam.longwill at gmail.com>
wrote:

> Agreed with Mr. West.
>
> On Fri, Mar 20, 2015 at 1:00 PM, Ben West <ben at gowasabi.net> wrote:
>
>> Echoing Adam's recommendation to distribute the load of 100+ clients over
>> multiple nodes set to non-overlapping channels, with each node wired back
>> to whatever gateway device with cat-5 lines.  That is, don't bother with
>> wireless meshing if you can avoid it.  A single 802.11 channel won't
>> sustain that many clients, much less the meshing OLSR traffic.  So, say 10
>> nodes spaced evenly throughout the conference venue, where immediately
>> adjacent nodes are set to furthest possible channels (e.g channel 1 and
>> 11).  Apply similar reasoning for dual-band access points; adjacent devices
>> need to not have their radios on adjacent frequencies.
>>
>> Also, you probably will want to turn the TX power on each node *down as
>> much as possible*, as they will be operating in a very noisy environment
>> at close spacing.  RX sensitivity is preferred over trying to drown out
>> noise with TX power.
>>
>> Finally, you'd want generous RAM available on the access points, so that
>> the firmware can service many clients.  Something like UBNT Rocket M2 (64MB
>> RAM), UBNT UniFi AP (64MB RAM), or even TP-Link TL-WDR4300 (128MB).  The
>> UBNT stuff would permit easier mounting on walls/poles, since the TP-Link
>> is only an indoor consumer-grade unit.
>>
>>
>>
>>
>> On Fri, Mar 20, 2015 at 10:32 AM, Adam Longwill <adam.longwill at gmail.com>
>> wrote:
>>
>>> There will be issues with any device accepting more than 35 connection
>>> requests at a time due to the nature on 802.11 in general. You're going to
>>> have plenty of congestion with more than that and probably have hidden node
>>> problem issues without RTS/ CTS in that situation.
>>>
>>> Commotion is is OpenWRT with some configurations and OLSR running on the
>>> mesh interface which will reduce airtime overall. If anything, you should
>>> mitigate this by having multiple radios on multiple channels with ethernet
>>> meshing instead of a wireless mesh interface.
>>> On 20 Mar 2015 11:11, "David Banks" <david.adam.banks at gmail.com> wrote:
>>>
>>>> Hello Everyone,
>>>>
>>>> Has anyone  had experience using routers running commotion in high
>>>> volume, single building settings? I'm organizing a conference set for next
>>>> month and thought this would be an interesting application. Anyone know of
>>>> good commotion-compatible hardware that's capable of accepting 100+
>>>> connection requests at a time?
>>>>
>>>> --
>>>> -db
>>>>
>>>> _______________________________________________
>>>> Commotion-discuss mailing list
>>>> Commotion-discuss at lists.chambana.net
>>>> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>>>>
>>>>
>>> _______________________________________________
>>> Commotion-discuss mailing list
>>> Commotion-discuss at lists.chambana.net
>>> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>>>
>>>
>>
>>
>> --
>> Ben West
>> http://gowasabi.net
>> ben at gowasabi.net
>> 314-246-9434
>>
>
>


-- 
-db
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20150320/c9db715c/attachment-0001.html>


More information about the Commotion-discuss mailing list