wpa_supplicant does not work properly with some USB adapters on WinXP

Jouni Malinen jkmaline at cc.hut.fi
Mon Aug 14 09:36:43 EDT 2006


On Mon, Aug 14, 2006 at 11:13:47AM +0300, Adrian Nistor wrote:

> I tracked the problem in the source code and it looks like media
> connect/disconnect events are not properly
> received by the supplicant for this kind of adapters (it works fine with the
> one embeded in the notebook
> but not with the one attached on USB). The output of the supplicant contains
> a lot of these messages: "NDIS: ignored event for another adapter".

Could you please send a wpa_supplicant debug file showing this?

> In function wpa_driver_ndis_event_process() the name of the adapter from the
> WMI event is compared to the
> description of the adapter (obtained from winpcap?) and the event is ignored
> if there is a mismatch.
> The problem was found to be here; in some cases the description of the
> adapter is not the same as the instance name in WMI
> (depends on driver manufacturer).

Yes, I'm aware of this issue, but have not found an easy fix for it so
far (or well, have not been motivated enough to search for one since I
don't have a card that triggers this behavior ;-).

> I propose a safer approach: modify
> ndis_events.c to send the
> name (UUID) of the interface (eg. {508692E1-7B72-43B7-ABBE-B2EAF2CDDCDE})
> with the event instead of the
> instance name from WMI, also modify wpa_driver_ndis_event_process() to make
> the comparison based on interface name
> instead of adapter description.

This is indeed what I would have wanted to do..

> The only tricky issue here is to find the
> UUID of the adapter when only the instance name from the WMI event is known.
> I finally managed to write the code that does this via some WMI queries.
> 
> This solved the problem entirely in my case and worked with 3 different
> brands of USB wireless cards.

That's great to hear!

> Has anyone experienced the same problem? Any alternative solutions?

Probably someone has. I haven't of alternative solutions and anyway,
what you described above sounds like the best solution (well, assuming
the changes in WMI code were not horrible).

> Currently my patch is quite dirty, but I can post it if somebody is
> interrested in it (maybe it can be integrated in the dev branch).

Please do post it. If needed, I can clean it up,  but anyway, I want to
get it merged into the development branch.

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the HostAP mailing list