From: Dan Williams <dcbw@redhat.com>
To: Brent Taylor <motobud@gmail.com>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
ath6kl@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Laptop disassociating by local choice (reason=17)
Date: Tue, 02 Dec 2014 17:32:08 -0600 [thread overview]
Message-ID: <1417563128.32003.8.camel@dcbw.local> (raw)
In-Reply-To: <CAP+RiCC4KmgNMGCiCzDeL_0-frGw7acoZf5FDv4OTmauQPU5Hw@mail.gmail.com>
On Tue, 2014-12-02 at 16:35 -0600, Brent Taylor wrote:
> 1417557229.339147: WPA: RSN IE in EAPOL-Key - hexdump(len=22): 30 14
> 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
> 1417557229.339179: WPA: RSN IE in Beacon/ProbeResp - hexdump(len=26):
> 30 18 01 00 00 0f ac 04 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac
> 02 00 00
> 1417557229.339192: WPA: RSN IE in 3/4 msg - hexdump(len=22): 30 14 01
> 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
On the STA side:
The RSN IE in the EAPOL-Key and the 3/4msg are the same, and contain
only the CCMP pairwise suite. The RSN IE in the Beacon/ProbeResp debug
message contains both CCMP and TKIP pairwise suites.
Earlier in the run we have:
1417557228.979261: WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00
00 0f ac 04 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
1417557228.979342: WPA: Set own WPA IE default - hexdump(len=22): 30
14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
which is where the extra TKIP bit comes from. I'm guessing this is from
wpa_supplicant_set_suites() because of the closely paired AP RSN IE/own
WPA IE calls.
Brent, is there any chance you can run the supplicant on the laptop with
"-dddt" to get *all* the debug messages? It seems the logs are missing
quite a few that could tell us where wpa_supplicant_set_suites() is
getting called.
Dan
next prev parent reply other threads:[~2014-12-02 23:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 18:12 Laptop disassociating by local choice (reason=17) Brent Taylor
2014-12-01 18:49 ` Brent Taylor
2014-12-01 19:00 ` Krishna Chaitanya
2014-12-02 19:18 ` Brent Taylor
2014-12-02 19:39 ` Krishna Chaitanya
2014-12-02 22:35 ` Brent Taylor
2014-12-02 23:32 ` Dan Williams [this message]
2014-12-02 23:43 ` Brent Taylor
2014-12-03 5:24 ` Kalle Valo
[not found] ` <CAP+RiCCE1Z96z6+YX=Cfnb0O3vGdnZeivJH5T3XQ5DWbCbbH_w@mail.gmail.com>
2014-12-03 5:37 ` Kalle Valo
2014-12-03 14:05 ` Brent Taylor
2014-12-03 16:58 ` Brent Taylor
2014-12-03 17:26 ` Brent Taylor
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=1417563128.32003.8.camel@dcbw.local \
--to=dcbw@redhat.com \
--cc=ath6kl@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=motobud@gmail.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).