From: Andres Bertens <abertensu@yahoo.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
ipw3945-devel@lists.sourceforge.net
Subject: Re: FW: [ipw3945-devel] iwl3945: disassociation from AP (reason=4) andtimeout, a solution
Date: Tue, 01 Apr 2008 09:45:15 -0400 [thread overview]
Message-ID: <47F23C6B.6060205@yahoo.com> (raw)
In-Reply-To: <1207051434.5143.58.camel@johannes.berg>
Johannes Berg wrote:
>>>> After browsing the internet, I found a lot of people with the same
>>>> problem and no solution. So, I dived into the code and found a simple
>>>> solution: ignore disassociation. When a new request arrives to the
>>>> wireless, a reconnection is done automatically.
>> Ignoring the disassociation from the AP is suspect... wouldn't the AP
>> be releasing resources associated with the station, requiring a
>> reassociate/reauth from the station? Reason 4 seems to mean "Inactivity
>> timer expired and station was disassociated".
>
> Indeed.
>
>> A better solution would be to queue up a reassocation worker if the AP
>> kicked you off for reason 4, maybe?
>
> It would think so, yes.
>
> johannes
Reason=4 is in fact "Inactivity timer expired and station was
disassociated". According to my router log:
"Tuesday April 01, 2008 09:08:54 Disassociated: 00-19-D2-4F-22-4D
because idle 300 seconds"
Indeed, the default behaviour goes for a reassocation but my hw/sw
combination (intel3945/dlink/wep) fails with a status=17 (AP unable to
handle new status). After 3 tries, it dies with an AP association
timeout. From there is no recovery till I set the interface down and up.
That's why I solved it (perhaps not in the best way) ignoring the
disassociation. Now it works.
Andres
next prev parent reply other threads:[~2008-04-01 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 21:17 FW: [ipw3945-devel] iwl3945: disassociation from AP (reason=4) andtimeout, a solution Chatre, Reinette
2008-03-31 21:41 ` Dan Williams
2008-04-01 12:03 ` Johannes Berg
2008-04-01 13:45 ` Andres Bertens [this message]
2008-04-01 16:42 ` Johannes Berg
2008-04-02 15:35 ` Andres Bertens
2008-04-03 22:03 ` Andres Bertens
2008-04-04 11:46 ` Tomas Winkler
2008-04-01 14:25 ` [ipw3945-devel] FW: " John W. Linville
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=47F23C6B.6060205@yahoo.com \
--to=abertensu@yahoo.com \
--cc=dcbw@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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).