<div dir="ltr">Hi Ben,<div><br></div><div>Thanks for the suggestion. I will check them out. I do like to ask your opinion about the following:</div><div><br></div><div>Several new ARM boards with 8 cores that is coming out have USB 3.0 build-in. On-board memory will start from 2GB and some might have 4GB. Do you think USB 3.0 WiFi dongle with 8 core ARM board might provide good performance?</div>
<div><br></div><div>We will get some WiFi dongle with big antenna or modify it and graft some big antenna onto it. </div><div><br></div><div>Driver might be an issue. We do not know until we have the board and WiFi dongle to run some test.</div>
<div><br></div><div>Paul</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 12, 2014 at 12:15 AM, Ben West <span dir="ltr"><<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Wow, that would be a lot of CPU and RAM behind a single 802.11n radio. Given at host machine with that many resources, I think you may find the USB dongle itself becoming a bottleneck far before the host CPU sees any significant load. The USB protocol stack itself (e.g. the ath9k_htc driver) is going to impose limitations on throughput in and out of the dongle, likely to be far less than the USB link speed. Embedded nodes use faster bus interfaces such like mini-PCI for this reason. <br>
<br>Also, you would be sacrificing some channel capacity if your USB dongle has only 1 RP-SMA port (making 2x2 MIMO unavailable), or if it uses itty bitty internal patch antennae.<br><br></div>For a node capable of hosting 30-50 clients, here is an ARM9-based single board computer, with a mini-PCI slot:<br>
<a href="http://www.gateworks.com/product/item/laguna-gw2388-4-network-processor" target="_blank">http://www.gateworks.com/product/item/laguna-gw2388-4-network-processor</a><br><br></div>Likewise, here is a mini-PCI 802.11n radio from UBNT. Two coaxial jacks for antenna diversity:<br>
<a href="http://shop.bizsyscon.com/ubiquiti-sr71-12-mimo-802-11b-g-n-2ghz-mini-pci/" target="_blank">http://shop.bizsyscon.com/ubiquiti-sr71-12-mimo-802-11b-g-n-2ghz-mini-pci/</a><br><br><div><div>This bug ticket does suggest at least one person has met moderate success running both of these units together under OpenWRT:<br>
<a href="https://dev.openwrt.org/ticket/13465" target="_blank">https://dev.openwrt.org/ticket/13465</a><br><br></div><div>Also, there should be other options for single board computer + mini-PCI with OpenWRT support out there, if that is your host OS of choice.<br>
</div><div><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 10, 2014 at 2:30 AM, Paul Liu <span dir="ltr"><<a href="mailto:paulsc.liu@gmail.com" target="_blank">paulsc.liu@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Ben,<div><br></div><div>Thank you for your feedback. We will review our overall deployment design.</div>
<div><br></div><div>Here is some additional information. We will build a customized node. The prototype is using a dual core ARM cpu with 2GB ram, gigabyte Ethernet as <span style="font-family:arial,sans-serif;font-size:12.666666984558105px">wired backhaul</span>. We will hookup USB WiFi dongle to service the clients. </div>
<div><br></div><div>We do plan to test wireless backhaul and probably run it on <span style="font-family:arial,sans-serif;font-size:12.666666984558105px">5.8GHz radios.</span></div><div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px">Right now the design call for each node to support 30 to 50 clients. We will try to find out what kind of usage scenario is possible. Data only? with voice? with video? How will transfer large data affect the performance?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px">Cheers,</span></div><div>Paul</div><div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:12.666666984558105px">If it is necessary, we can use quad cores or 8 cores ARM CPU.</span></div></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Sat, May 10, 2014 at 1:10 AM, Ben West <span dir="ltr"><<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">My recommendation, from operating a mesh network with firmware very similar to Commotion, that serves ~100 people daily, would be to focus on how many mesh nodes you would need to deploy. Likewise, since there is no way to fit 2000 users on a single 2.4GHz channel, you would be needing to segment such a large deployment into pocket meshes, e.g. a handful of nodes in each mesh, with adjacent meshes programmed to non-overlapping channels. Backhaul between these pocket meshes could be done with 5.8GHz radios, or wired backhaul depending on your situation.<br>
<br>To help with estimating how many nodes you'd need, it's fair to assume each node could only support up to 5 (or possibly 10) simultaneous clients before either the node itself exhausts its RAM (only 32Mbytes onboard memory) or before the particular channel used by that ( node + its neighboring nodes + all clients ) becomes saturated.<br>
<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Fri, May 9, 2014 at 11:58 AM, Paul Liu <span dir="ltr"><<a href="mailto:paulsc.liu@gmail.com" target="_blank">paulsc.liu@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Has anyone had the experience of building a commotion network that can support 2000 concurrent users?<div>
<br></div><div>Any advice on how to build it, potential pit fall? total equipment cost? </div><div><br>
</div><div>Best Regards</div><span><font color="#888888"><div>Paul Liu</div></font></span></div>
<br></div></div>_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
<a href="tel:314-246-9434" value="+13142469434" target="_blank">314-246-9434</a><br>
</div>
</font></span></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
314-246-9434<br></div>
</div>
</div></div></blockquote></div><br></div>