From: mabbas <mabbas@linux.intel.com>
To: linux-wireless@vger.kernel.org
Subject: repeat scanning could cause disassoc
Date: Fri, 06 Jul 2007 14:26:04 -0700 [thread overview]
Message-ID: <468EB36C.10508@linux.intel.com> (raw)
Hi
If I keep repeating scanning for like 4 times in the raw, the mac80211
can disassociated because No ProbeResp.
looking at the rx patch if we are scanning we wont pass
ieee80211_rx_h_passive_scan which only will deliver
beacon and probe request, which what we want, except that we only update
last_rx in the function
ieee80211_rx_h_sta_process which is two functions down rx handlers.
In iwlwifi we do perform hw scan, in this command if scan takes a long
time, and we are associated, it will tunes to associated channel to
allow getting beacons for a period of time, then continue with scanning.
we do receive beacons on the associated
channel but mac80211 never update last_rx causing the disassociation.
I wonder if we can move ieee80211_rx_h_sta_process before
ieee80211_rx_h_passive_scan or at least the rx_last
update part.
Thanks
Mohamed
next reply other threads:[~2007-07-06 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 21:26 mabbas [this message]
2007-07-10 23:11 ` repeat scanning could cause disassoc Johannes Berg
[not found] ` <b3153e950707111616r7f3f36a2x7a262f41afce396c@mail.gmail.com>
2007-07-12 20:43 ` Johannes Berg
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=468EB36C.10508@linux.intel.com \
--to=mabbas@linux.intel.com \
--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).