[hostap driver] not authenticating when used w/ wpa-supplicant / network-manager

[Andrew Jorgensen]

On 8/14/07, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-08-14 at 08:51 -0600, Andrew Jorgensen wrote:
> The driver is not able to associate with the network.  When doing this,
> run "iwevent" and post the output.  If you're doing a plain
> wpa_supplicant run with a minimal network block for an unencrypted
> network, then the possibility the driver got borked exceeds the
> possibility that wpa_supplicant is at fault, though it can't be ruled
> out.

I was assuming that the hostap driver (hostap_cs in my case) was at fault.

# iwevent
Waiting for Wireless Events from interfaces...
10:02:44.966222   wlan1    Set ESSID:""
10:02:44.966778   wlan1    Set Encryption key:off
10:02:44.994628   wlan1    Set ESSID:""
10:02:45.005041   wlan1    Set Encryption key:off
10:02:46.032745   wlan1    Set ESSID:""
10:02:46.044150   wlan1    Set Encryption key:off
10:02:48.161741   wlan1    Set Mode:Managed
10:02:48.446992   wlan1    Set Mode:Managed
10:02:48.468693   wlan1    Set Frequency:2.412 GHz (Channel 1)
10:02:48.508276   wlan1    Set ESSID:"Novell"
10:02:58.937544   wifi0    Scan request completed
10:03:01.536661   wlan1    Set Mode:Managed
10:03:01.558983   wlan1    Set Frequency:2.412 GHz (Channel 1)
10:03:01.590626   wlan1    Set ESSID:"Novell"
10:03:12.019031   wifi0    Scan request completed
10:03:14.620635   wlan1    Set Mode:Managed
10:03:14.642986   wlan1    Set Frequency:2.412 GHz (Channel 1)
10:03:14.678441   wlan1    Set ESSID:"Novell"
10:03:25.062026   wifi0    Scan request completed
10:03:27.708629   wlan1    Set Mode:Managed
10:03:27.730958   wlan1    Set Frequency:2.412 GHz (Channel 1)
10:03:27.766624   wlan1    Set ESSID:"Novell"
10:03:38.149908   wifi0    Scan request completed
10:03:40.796526   wlan1    Set Mode:Managed
10:03:40.819138   wlan1    Set Frequency:2.412 GHz (Channel 1)
10:03:40.850624   wlan1    Set ESSID:"Novell"
10:03:48.487518   wlan1    Set ESSID:""
10:03:48.571150   wlan1    Set Encryption key:off
10:03:59.854249   wifi0    Scan request completed

> If there's any way to enable debugging of orinoco and get some debug
> output as to _why_ the driver can't associate, that's the best thing to
> do.  Some drivers are sensitive to the ordering of WEXT calls, others
> are stupid and require iwpriv options to be called, etc.  The only thing
> that's really useful in a situation like this is driver debug output.

As stated above I'm using the hostap driver.  There doesn't appear to
be a load-time parameter to enable debugging.  I'll try to recompile
the driver.