From: Johannes Berg <johannes@sipsolutions.net>
To: Samuel Sieb <samuel@sieb.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Max clients on wifi access point with 7265
Date: Wed, 14 Feb 2018 23:36:24 +0100 [thread overview]
Message-ID: <1518647784.21268.4.camel@sipsolutions.net> (raw)
In-Reply-To: <4f048d04-5f25-caa1-51b3-dcb14baf36da@sieb.net> (sfid-20180214_231259_285834_62D716E2)
On Wed, 2018-02-14 at 14:04 -0800, Samuel Sieb wrote:
>
> As a general question, is there a standard way to determine this limit
> for any particular hardware?
That's a good question, but I don't think there is.
johannes
next prev parent reply other threads:[~2018-02-14 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 10:55 Max clients on wifi access point with 7265 Mickaël PANNEQUIN
2018-02-14 11:30 ` Johannes Berg
2018-02-14 22:04 ` Samuel Sieb
2018-02-14 22:36 ` Johannes Berg [this message]
2018-02-14 22:38 ` Steve deRosier
2018-02-19 6:07 ` Kalle Valo
2018-02-19 9:26 ` Luca Coelho
2018-02-19 11:18 ` Luca Coelho
2018-02-27 8:33 ` Kalle Valo
2018-02-27 17:56 ` Steve deRosier
2018-02-28 12:14 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1518647784.21268.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=samuel@sieb.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).