From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Kalle Valo <Kalle.Valo@nokia.com>,
Jouni Malinen <j@w1.fi>
Subject: Re: Problem with IEEE80211_MONITORING_INTERVAL
Date: Thu, 16 Apr 2009 03:12:05 +0200 [thread overview]
Message-ID: <1239844325.11795.50.camel@violet> (raw)
In-Reply-To: <1239842656.25334.20.camel@johannes.local>
Hi Johannes,
> > > After a long debugging session with Reinette we finally tracked down
> > > what is going on here. A full scan with this card takes 7-9 seconds and
> > > that seems to be too long and trigger IEEE80211_MONITORING_INTERVAL
> > > which then deauthenticates us with the AP (reason=6).
> >
> > Yeah, this is a bug. We analysed this problem a couple of days ago and I
> > thought Kalle was going to fix it -- maybe he forgot. I forgot what
> > exactly it was and how to fix it, hmm. Right now I'm confused and can't
> > seem to reproduce my analysis. I thought it had something to do with
> > using a different timer but we do seem to use the regular mgd.timer, so
> > I'm not sure.
>
> Hmm. Can't seem to find what's going on -- can you enable
> CONFIG_MAC80211_VERBOSE_DEBUG and check for the beacon loss messages?
I did that already and yes, I see the beacon loss message. Increasing
IEEE80211_MONITORING_INTERVAL to 10 seconds fixes this, but that can't
be the real solution for it.
Also even when it deauth, it should then be able to authenticate and
associate again. If I end up in this situation basically only a reboot
fixes it.
Regards
Marcel
next prev parent reply other threads:[~2009-04-16 1:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 23:21 Problem with IEEE80211_MONITORING_INTERVAL Marcel Holtmann
2009-04-16 0:21 ` Johannes Berg
2009-04-16 0:44 ` Johannes Berg
2009-04-16 1:12 ` Marcel Holtmann [this message]
2009-04-16 1:08 ` Marcel Holtmann
2009-04-16 1:16 ` Johannes Berg
2009-04-16 6:14 ` Kalle Valo
2009-04-16 9:12 ` Johannes Berg
2009-04-16 9:43 ` Johannes Berg
2009-04-16 9:49 ` Kalle Valo
2009-04-16 9:58 ` Johannes Berg
2009-04-16 9:59 ` Kalle Valo
2009-04-16 10:04 ` Johannes Berg
2009-04-16 10:08 ` Kalle Valo
2009-04-16 10:18 ` Johannes Berg
2009-04-16 10:23 ` Kalle Valo
2009-04-16 9:46 ` Johannes Berg
2009-04-20 17:13 ` Marcel Holtmann
2009-04-20 17:20 ` Johannes Berg
2009-04-20 17:26 ` Marcel Holtmann
2009-04-20 17:32 ` Johannes Berg
2009-04-21 19:56 ` Marcel Holtmann
2009-04-21 21:19 ` Johannes Berg
2009-04-22 7:32 ` Marcel Holtmann
2009-04-22 9:03 ` Johannes Berg
2009-04-22 9:12 ` Marcel Holtmann
2009-04-22 9:45 ` Johannes Berg
2009-04-22 11:17 ` Marcel Holtmann
2009-04-22 11:53 ` Marcel Holtmann
2009-04-22 12:14 ` Johannes Berg
2009-04-22 12:56 ` Marcel Holtmann
2009-04-22 13:27 ` John W. Linville
2009-04-22 17:35 ` reinette chatre
2009-04-22 5:04 ` Kalle Valo
2009-04-22 7:27 ` Marcel Holtmann
2009-04-20 18:29 ` Jouni Malinen
2009-04-21 10:47 ` Marcel Holtmann
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=1239844325.11795.50.camel@violet \
--to=marcel@holtmann.org \
--cc=Kalle.Valo@nokia.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).