Hi acim, thx for invitation
I am not a member but I'll do it right away.
I am talking about 802.11b.
CPU can't help here, it's a card actually the one that can't process a lot of connections, packets/second.
As cibernet wrote it depends what kind of traffic you have.
So basically number of associated clients is not a problem as far as amount of traffic is not killin' performance.
I have APs with 40 clients connected at the same time, they use regular http, icq, mirc etc. and APs are working great (2mbit/s average comsumption).
On other hand, I have APs with 20 clients, but these guys are Internet killers (p2p, all sorts of junk traffic) and AP consumption is ~0.5mbit/s.
Remember, just one client with junk traffic can kill your AP.
So, filter viruses, use mangle, queue tree, limit concurrent connections per IP, turn off default forwarding, fight for your AP
There are people here sayin' I don't want to limit my costumers!!!
Well, I'm doing this for their own good! They can't get wild on AP!
They can use internet as God said! There most be some quality of service and priorities. It could be called Order of da House
I drink like a pirate and smoke like a hippie...