From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Dan Williams <dcbw@redhat.com>, Michael Buesch <mb@bu3sch.de>,
linville@tuxdriver.com, netdev@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] softmac: Fix WX and association related races
Date: Thu, 28 Sep 2006 10:52:24 -0500 [thread overview]
Message-ID: <451BEFB8.8000402@lwfinger.net> (raw)
In-Reply-To: <200609281135.24720.flamingice@sourmilk.net>
Michael Wu wrote:
> On Thursday 28 September 2006 11:16, Larry Finger wrote:
>> First of all, my problem is quite likely caused by a buggy AP. It is a
>> Linksys WRT54G V5, which is one of those with a VxWorks kernel, not Linux.
>> I have already reported one bug to Linksys, which they have neither
>> acknowledged nor fixed! In that case, SoftMAC had to be modified as a
>> work-around.
>>
> These APs are truly bad. Hacking linux into it (DD-WRT) helps a bit, but
> wireless often seems to fail *completely* at times.
I had very good luck with my first AP, a Linksys WRT54G V1, that I bought a second when the power
supply failed in the first. Little did I know that a VxWorks license costs less than the extra
memory needed to run Linux. Or was it to defeat the open-source alternatives for the AP?
>> I don't know why the deauthentication is being sent. The reason is not
>> logged, which will be my first change in the code. The second place to look
>> is why SoftMAC reports the network is unknown when the MAC printed is that
>> of my AP.
>>
> The deauth reason code is usually 6 or 7.. IIRC, it is 6: Class 2 Frame from
> Non Authenticated STA. The AP just forgets you're associated. However, I
> think that was from when I had a v3 WRT54G.
I already have modified SoftMAC to log the reason. Now I have to wait for the event to happen.
> I made sure the old adm8211 softmac stack had a very good set of printks to
> report these sort of things. :) Many APs do funny things..
Thanks for the tip. It is unfortunate that the Linux code has to work around all the closed-source
other stuff!
Larry
next prev parent reply other threads:[~2006-09-28 15:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 15:26 [PATCH] softmac: Fix WX and association related races Michael Buesch
2006-09-27 16:18 ` Larry Finger
2006-09-27 17:50 ` Michael Buesch
2006-09-27 21:11 ` Christian
2006-09-27 21:21 ` Christian
2006-09-27 22:23 ` Benjamin Herrenschmidt
2006-09-28 0:43 ` Larry Finger
2006-09-28 1:04 ` Benjamin Herrenschmidt
2006-09-28 4:09 ` Larry Finger
2006-09-28 12:55 ` Michael Buesch
2006-09-28 14:19 ` Dan Williams
2006-09-28 14:27 ` Johannes Berg
2006-09-28 14:37 ` Dan Williams
2006-09-28 14:43 ` Michael Buesch
2006-09-28 14:52 ` Dan Williams
2006-09-28 15:13 ` Michael Buesch
2006-09-28 17:33 ` Jouni Malinen
2006-09-28 15:16 ` Larry Finger
2006-09-28 15:29 ` Michael Buesch
2006-09-28 15:35 ` Michael Wu
2006-09-28 15:52 ` Larry Finger [this message]
2006-09-28 16:31 ` Jason Lunz
2006-09-28 17:04 ` Larry Finger
2006-09-28 17:14 ` Michael Buesch
2006-09-28 17:40 ` Larry Finger
2006-09-28 14:43 ` Johannes Berg
2006-09-27 22:20 ` Benjamin Herrenschmidt
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=451BEFB8.8000402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@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).