linux-kernel - Re: 2.6.29+ ath5k connect disconnect cycles?

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: <20090407102927.225890@gmx.net>
Date:	Tue, 07 Apr 2009 12:29:27 +0200
From:	"Markus Koßmann" <mkossmann_ml1@....de>
To:	Soeren Sonnenburg <sonne@...ian.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Tulio Magno Quites Machado Filho <tuliom@...tes.com.br>
Subject: Re: 2.6.29+ ath5k connect disconnect cycles?


> On Mon, 2009-04-06 at 21:55 +0200, Tulio Magno Quites Machado Filho
> wrote:
> > On Apr 06 09 10:55, Soeren Sonnenburg wrote:
> > > does anyone else observer strange connect disconnect cycles with
> ath5k?
> > > I have two different notebooks here one with an AR5414 and one with
> some
> > > 2424 (?) chipset both having the same problems to connect...
> > 
> > Hello Soeren,
> > 
> > Is there any information from dmesg?
> 
> I am seeing cycles of
> 
> airport: deauthenticated (Reason: 2)
> airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
> airport direct probe responded
> airport: authenticate with AP XX:XX:XX:XX:XX:XX
> airport: authenticated
> airport: associate with AP XX:XX:XX:XX:XX:XX
> airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0
> aid=79)
> airport: associated
> airport: deauthenticated (Reason: 2)
> airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
> airport direct probe responded
> airport: authenticate with AP XX:XX:XX:XX:XX:XX
> airport: authenticated
> airport: associate with AP XX:XX:XX:XX:XX:XX
> airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0
> aid=81)
> airport: associated
> airport: deauthenticated (Reason: 2)
> airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
> airport direct probe responded
> airport: authenticate with AP XX:XX:XX:XX:XX:XX
> airport: authenticated
> airport: associate with AP XX:XX:XX:XX:XX:XX
> airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0
> aid=82)
> airport: associated
> airport: deauthenticated (Reason: 2)
> ...
> 
> Not sure about the involvement of network-manager here... but I see that
> the device gets a valid IP via dhcp.
> 
I've seen such cycles also with intel ipw5300 WLAN and using ifconfig to start the network. To get WLAN working again, I have to ifdown wlan0 , unload and reload the driver module and  finally ifup wlan0. So it's probably neither a ath5k nor a network-manager problem.
--
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/