To put it slightly more clear, you can have 128 associations to the APP. However it's highly unlikely that all 128 will want to hit the net all at the same time. The theoretical limit of how many can be on and transferring at the same time depends on several factors.
- What kind of uploading/downloading are they doing? (just casual surfing? downloading Microsoft Service Pack 238? hosting a multiplayer game with 30 of their friends? - What kind of bandwidth limiting you are using, and at what point(s) in your network are you doing the limiting? - Luck. The luck factors in where you are lucky if 50+ of the 128 possible clients aren't all downloading the Microsoft Service Pack at the same time. ;-) The bandwidth limiting opens an entirely new can of worms on most lists, but here goes. (In my humble opinion) For small networks of lets say 2-4 pops that don't have more than 2 hops in them to your noc, the best place to limit is at the noc. You always want the client radios talking to the APs at the fastest rate possible so they get their packets moved across and then they are out of the way for the next client to get theirs. In small networks it pays to have the bandwidth limiter at the noc for more centralized management. Once your network grows beyond that, you'll want to place bandwidth management out at the legs of those POPs. Let's say for example you have a network of 4 backhaul links out to 4 POPs, and those have backhaul links out 1 or 2 hops to more POPs. Your bottleneck in the network is now all at the noc where your one bandwidth limiter is sitting. If you move that out to some point along those 4 backhaul links (1 bandwidth limiter per link) then you have more granular control over those links and the customers behind them. I hope this makes sense and helps some. If I'm typing to much, going to far, or just letting my finger stretch to much this morning, I apologize for the running off at the keyboard... Kevin Summers KISTech Internet Services Inc. www.kistech.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Blazen Wireless Sent: Monday, July 28, 2003 7:45 AM To: [EMAIL PROTECTED] Subject: Re: [smartBridges] How many clients can be connected to AP? Wow only 20 -30? I heard one wisp had about 40 on there. Motorola advertises 200 per each of their access points? Can SB confirm if this is true only 20-30 this puts a damper on things.. now say I had one main AP with 20 customers on it and then a remote AP backhauled of the main AP and the remote AP had say 30 customers on it would that be a total of 50 the main AP is seeing or would it be like having 21 on the main ap? Thanks ----- Original Message ----- From: Colin Watson To: [EMAIL PROTECTED] Sent: Monday, July 28, 2003 7:38 AM Subject: Re: [smartBridges] How many clients can be connected to AP? usually the number is about 2048 clients per AP, well, 2048 MAC addresses - you should have no artificial limits unless you imposed them yourself in the configuration? - Generally thoughy you shouldn't have more then 20-30 people per AP usually otherwise your clients may expierence slowdown, - your mileage may vary however . ----- Original Message ----- From: Marcin Żelaznowski To: [EMAIL PROTECTED] Sent: Monday, July 28, 2003 1:31 PM Subject: [smartBridges] How many clients can be connected to AP? In our wireless network, made on SB Air Point Pro we can't connect more then 12 -13 clients to one AP. When 14-th client is trying to connect to the AP, one of previously connected looses his connection. Any ideas why? The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
