From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felix Fietkau Date: Tue, 09 Jul 2013 11:52:33 +0200 Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA In-Reply-To: <51DBD921.3040704@rempel-privat.de> References: <51DA79B6.8030702@djardin.de> <51DBCE01.5030406@djardin.de> <51DBCEBE.7010405@rempel-privat.de> <51DBD55B.2010204@openwrt.org> <51DBD921.3040704@rempel-privat.de> Message-ID: <51DBDD61.8010503@openwrt.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 2013-07-09 11:34 AM, Oleksij Rempel wrote: > Am 09.07.2013 11:18, schrieb Felix Fietkau: >> On 2013-07-09 10:50 AM, Oleksij Rempel wrote: >>> How replacing AP with about MESH or AdHock+BATMAN? >> Why? That sounds like a recipe for disaster to me (at least for >> conference networks). The ath9k_htc stuff can't handle more peers in >> mesh/ad-hoc than clients in AP mode. >> In setting up a conference network, you have to think about what the >> primary bottleneck is. When using consumer APs, the bottleneck isn't >> CPU/RAM, it's usually limited channel airtime! >> >> - Felix >> > > Not with ath9k_htc. AdHock+BATMAN can be split in different groups on > different channels. ath9k_htc can be used as STA to primer AP and > second interface on some laptops. But sure -- it is worst case scenario > with no extra cost. What does this have to do with handling wifi clients of 200-300 participants? - Felix