<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Kev, Karl thanks you were dead right, not only for all consumer
AP's, but it turns out even on meshing systems the advice is to
ensure coverage that keeps concurrent connections below 15 per node.<br>
<br>
We worked around the issue by installing a number of AP's and
allocating people evenly to the AP's.<br>
<br>
Hope I can make a KLUG meeting one of these days!<br>
<br>
Alan<br>
<br>
==================================<br>
<br>
<div class="moz-cite-prefix">On 06/06/14 18:56, Kevin Groves wrote:<br>
</div>
<blockquote cite="mid:539200B4.9060707@cix.co.uk" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I would agree too many for one AP
with all the hand shaking and such. Any possibility of a few
more and making a mesh?<br>
<br>
Kev,<br>
<br>
On 06/06/14 17:09, Karl Buckland wrote:<br>
</div>
<blockquote
cite="mid:CAOe9xYAmni-Lk0zmNz5cfJjZR4ZLLz2NYCiMG_axX819mHugUA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Alan,
<div><br>
</div>
<div>Regardless of the issue of devices getting registered, I
would have thought that 60 devices would be completely
oversubscribing a wireless access point. On a 54 mbps access
point in perfect conditions, those 60 clients would get
about 900kbps each. Then you have TCP overheads on top of
that. Even with a faster access point, the timing
interference between all those radios trying to broadcast at
once becomes a big problem. And that's with perfect
conditions. More than likely, it's much worse than that. Are
the devices that are registering working properly? I
would've thought they would be struggling and you'd need at
least two access point on different channels.<br>
</div>
<div><br>
</div>
<div>Sorry I know that isn't answering your questions
directly, but I looked into something similar previously and
thought this might help.</div>
<div><br>
</div>
<div>Karl</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 6 June 2014 16:58, Alan <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:alan@hipnosi.org" target="_blank">alan@hipnosi.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi all,<br>
<br>
Running into a weird problem trying to use about 60
wireless devices simultaneously on a single ESSID and I
wonder if anyone has some experience of any issues or
limitations in this regard..<br>
<br>
I am helping out a local cell of <a
moz-do-not-send="true" href="http://coderdojo.com"
target="_blank">coderdojo.com</a>, as soon as more than
20 or so devices connect to their wireless, no more new
devices can associate (even if existing devices get off).<br>
<br>
Initially I thought it was a problem with the wireless AP
on the cheap ADSL router, so I set up a separate wireless
AP relaying the DHCP from the router (yes the router has a
large pool - 192.168.1.5-250). Still during the next
session the same issue again.<br>
<br>
Following that I installed a Debian box running dnsmasq as
a DHCP server and NAT routing traffic on the AP to the
ADSL router - what do you know, same problem!<br>
<br>
The core issue is the inability of large numbers of
devices to associate with the wireless AP (have tried a
few different consumer wireless AP's by now - all with
same symptoms)<br>
<br>
The next dojo is tomorrow and I will be there to diagnose
onsite this time, but if anybody has any heads-ups about
large wireless networks I'd really appreciate the info.<br>
<br>
Alan<br>
</blockquote>
</div>
</div>
</blockquote>
</blockquote>
<br>
</body>
</html>