Wireless event: cmd=0x8c00 len=20

[Jouni Malinen]

On Thu, Jun 24, 2004 at 09:30:39AM -0400, Brian J. Murrell wrote:
> On Wed, 2004-06-23 at 20:24 -0700, Jouni Malinen wrote:
> > nothing else, I could add a workaround for this so that wpa_supplicant
> > could trigger a join request if it detects that each TX packets gets
> > IWEVTXDROP status..
> 
> Seems a bit hackish, no?  If I could understand what the real problem is
> (with my very limited -- er, make that next to no knowledge of wifi) and
> it's something that needs to be addressed with a hardware vendor, I can
> try that route.

Well, yes, that's why I called it a workaround that could be used if
nothing else works ;-). One of the problems is that the station firmware
drops into somewhat odd mode when doing a scan request but not following
it with a join request. This kind of operation sounds reasonable thing
to do from my view point, so changing something in the firmware could be
useful. However, this is only happening with one roaming mode
("disabled").

> > I'm in process of changing wpa_supplicant to use a different roaming
> > mode to avoid this issue.
> 
> Hrm.  So is this actually a wpa_supplicant issue then and not with
> hardware/firmware?

I don't think it would be fair to put it that way, but let's say another
roaming mode (of the Prism2 firmware) could be a better choice and it
does not seem to suffer from the same issue (although, if I remember
correctly, it may have somewhat similar issues in a bit different case).
Anyway, I'm working on getting this to work with Host AP driver and
wpa_supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA