From: "Nick Kossifidis" <mickflemm@gmail.com>
To: "Helge Deller" <deller@gmx.de>
Cc: "Bob Copeland" <me@bobcopeland.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, mcgrof@gmail.com
Subject: Re: ath5k aborts wireless connections
Date: Sun, 30 Mar 2008 01:29:09 +0200 [thread overview]
Message-ID: <40f31dec0803291629v540badd2xb31ab92d860d9ea2@mail.gmail.com> (raw)
In-Reply-To: <200803272017.50126.deller@gmx.de>
2008/3/27, Helge Deller <deller@gmx.de>:
> On Thursday 27 March 2008, Bob Copeland wrote:
> > On Tue, Mar 25, 2008 at 09:11:05PM +0100, Helge Deller wrote:
> > > On Tuesday 25 March 2008, Bob Copeland wrote:
> > > > On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> > > > > Hello ppl, sory for the delay ;-)
> > > > >
> > > > > Are you using encryption ? I haven't got such errors on my tests (it
> > > > > might be that my setup is really simple) so far...
> > > >
> > > > I can't speak for Helge, but in my case yes - WPA-TKIP.
> > >
> > > Same here. WPA-PSK & TKIP.
> >
> > So, I turned off encryption here and did not get any "invalid Michael
> > MIC" messages while doing a large apt-get upgrade overnight. I do get
> > random pauses but nothing else in my dmesg.
> >
> > Helge, can you confirm disabling encryption makes the reset go away?
>
>
> Yes, I can confirm this.
>
> Without encryption everything worked pretty OK.
>
> I only faced one very small hickup, but ath5k reconnected immediately again, so I don't think this is a real problem:
>
>
> wlan1: authenticated
> wlan1: associate with AP 00:50:18:3b:2b:04
>
> wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x461 status=0 aid=1)
> wlan1: associated
> wlan1: No ProbeResp from current AP 00:50:18:3b:2b:04 - assume out of range
>
> wlan1: Initial auth_alg=0
> wlan1: authenticate with AP 00:50:18:3b:2b:04
> wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
> wlan1: authenticated
>
>
> Helge
>
Since we use software encryption for now we 'll need to trace this
inside base.c or higher on the stack. Anyone with similar problems
with other drivers that use software encryption ???
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
prev parent reply other threads:[~2008-03-29 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 10:29 ath5k aborts wireless connections Helge Deller
2008-03-24 19:44 ` John W. Linville
2008-03-25 15:52 ` Bob Copeland
2008-03-25 18:16 ` Nick Kossifidis
2008-03-25 19:16 ` Bob Copeland
2008-03-25 20:11 ` Helge Deller
2008-03-27 11:51 ` Bob Copeland
2008-03-27 19:17 ` Helge Deller
2008-03-29 23:29 ` Nick Kossifidis [this message]
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=40f31dec0803291629v540badd2xb31ab92d860d9ea2@mail.gmail.com \
--to=mickflemm@gmail.com \
--cc=deller@gmx.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
/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;
as well as URLs for NNTP newsgroup(s).