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: <1239097961.32048.484.camel@localhost>
Date:	Tue, 07 Apr 2009 11:52:41 +0200
From:	Soeren Sonnenburg <sonne@...ian.org>
To:	Tulio Magno Quites Machado Filho <tuliom@...tes.com.br>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	ath5k-devel <ath5k-devel@...ts.ath5k.org>
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.

Soeren
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
--
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/