linux-kernel - Re: iwlagn broken in next-20090514 and next-20090515

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: <1242663400.6530.18.camel@localhost.localdomain>
Date:	Mon, 18 May 2009 12:16:40 -0400
From:	Dan Williams <dcbw@...hat.com>
To:	reinette chatre <reinette.chatre@...el.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Nico -telmich- Schottelius <nico-linux-next@...ottelius.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	johannes@...solutions.net
Subject: Re: iwlagn broken in next-20090514 and next-20090515

On Mon, 2009-05-18 at 09:03 -0700, reinette chatre wrote:
> On Mon, 2009-05-18 at 00:15 -0700, Stephen Rothwell wrote:
> > Add cc's
> > 
> > On Fri, 15 May 2009 12:26:21 +0200 Nico -telmich- Schottelius <nico-linux-next@...ottelius.org> wrote:
> > >
> > > Kernel is not authenticating it against the AP anymore with
> > > messages like:
> > > 
> > > [16907.701634] wlan0: associate with AP 00:03:52:4e:f3:d1
> > > [16907.703669] wlan0: RX AssocResp from 00:03:52:4e:f3:d1 (capab=0x421 status=0 aid=5)
> > > [16907.703672] wlan0: associated
> > > [16907.729958] wlan0: disassociating by local choice (reason=3)
> 
> This is usually printed when your user application (wpa_supplicant,
> network manager, etc.) goes down or disassociates.

Yeah, this is normal and indicates that the supplicant called
SIOCGIWMLME, which could either be triggered internally by the
supplicant, or even more likely, because NetworkManager requests that
the supplicant disconnects nicely before switching networks or taking
the connection down.

Dan

> > > [16907.852112] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 1
> > > [16908.052086] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 2
> > > [16908.055331] wlan0 direct probe responded
> > > [16908.055335] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.256065] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.453689] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.656037] wlan0: authentication with AP 00:03:52:1b:f8:31 timed out
> 
> Don't know what is going on here. Could your AP be out of reach or not
> responding?
> 
> > > 
> > > Also wpa_supplicant is not happy:
> > > 
> > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > 
> 
> There were some changes recently to this ioctl, but I am not familiar
> with details. Johannes will know.
> 
> Reinette
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
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/