linux-kernel - Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1375802993.8219.26.camel@jlt4.sipsolutions.net>
Date:	Tue, 06 Aug 2013 17:29:53 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	sedat.dilek@...il.com
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	wireless <linux-wireless@...r.kernel.org>
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]

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@...il.com> wrote:
> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg <johannes@...solutions.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/