From: Johannes Berg <johannes@sipsolutions.net>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]
Date: Tue, 06 Aug 2013 17:29:53 +0200 [thread overview]
Message-ID: <1375802993.8219.26.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUVuOqdZUGy2ALAF1CehOqYdr7rtEsXhqNvDtYEns2BuRQ@mail.gmail.com> (sfid-20130806_172725_033196_729FC01D)
On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> >>
> >>
> >>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
> >>
> >> Hmm, that looks different? There no longer is anything about "PSK might
> >> be wrong", but now just disconnections by the AP, which unfortunately
> >> indicate no reason.
> >>
> >> When was it working last?
> >>
> >
> > next-20130801 was OK here.
> >
>
> What about these lines?
>
> Aug 6 17:03:37 fambox kernel: [ 134.575120] wlan0: deauthenticated
> from 00:04:0e:e4:00:3d (Reason: 1)
> Aug 6 17:03:37 fambox wpa_supplicant[2424]: wlan0: Event DEAUTH (12) received
> Aug 6 17:03:37 fambox wpa_supplicant[2424]: wlan0: Deauthentication
> notification
> Aug 6 17:03:37 fambox wpa_supplicant[2424]: Deauthentication frame
> IE(s) - hexdump(len=0): [NULL]
> Aug 6 17:03:37 fambox wpa_supplicant[2424]: wlan0: WPA: 4-Way
> Handshake failed - pre-shared key may be incorrect
> Aug 6 17:03:37 fambox NetworkManager[2431]: <info> (wlan0):
> supplicant interface state: 4-way handshake -> disconnected
Yeah but before you had a local deauth request, this time it's the AP
kicking you off.
I really don't know. Can you try something like wireless-testing maybe?
-next could have any kind of breakage I guess ...
johannes
next prev parent reply other threads:[~2013-08-06 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:51 linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ] Sedat Dilek
2013-08-06 13:54 ` Johannes Berg
2013-08-06 14:02 ` Sedat Dilek
2013-08-06 14:46 ` Sedat Dilek
2013-08-06 14:50 ` Johannes Berg
2013-08-06 14:56 ` Sedat Dilek
2013-08-06 14:57 ` Johannes Berg
[not found] ` <1375801059.8219.24.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-08-06 14:59 ` Sedat Dilek
2013-08-06 15:09 ` Sedat Dilek
2013-08-06 15:18 ` Johannes Berg
2013-08-06 15:20 ` Sedat Dilek
2013-08-06 15:27 ` Sedat Dilek
2013-08-06 15:29 ` Johannes Berg [this message]
2013-08-06 15:43 ` Sedat Dilek
2013-08-06 15:58 ` Sedat Dilek
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=1375802993.8219.26.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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