From: Josh Lehan <krellan@krellan.com>
To: Paul Stewart <pstew@google.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Distinguishing wrong password from other failure to connect?
Date: Sat, 13 Nov 2010 18:36:55 -0800 [thread overview]
Message-ID: <4CDF4B47.2000207@krellan.com> (raw)
In-Reply-To: <AANLkTikHOsYPwU0J-bYFGQamCS4CVUP5T_B1yGLCjmD5@mail.gmail.com>
On 11/12/2010 09:21 AM, Paul Stewart wrote:
> The "reason=xx" codes are standardized by 802.11. However when
> reading such messages, one needs to be careful to note which party
> sent that reason code. There are times when the AP sends this
> message, and other times where the station sends it as it departs.
Thanks for the information. Is there a guideline as to what messages
indicate wrong settings by the user (wrong password, etc.)?
Basically, I'm trying to know where to pin the blame: on the user's
wrong password, or on the network itself.
Josh
next prev parent reply other threads:[~2010-11-14 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 7:25 Distinguishing wrong password from other failure to connect? Josh Lehan
2010-11-12 16:51 ` Johannes Berg
2010-11-12 17:21 ` Paul Stewart
2010-11-14 2:36 ` Josh Lehan [this message]
2010-11-13 10:34 ` Jouni Malinen
2010-11-14 2:47 ` Josh Lehan
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=4CDF4B47.2000207@krellan.com \
--to=krellan@krellan.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pstew@google.com \
/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).