Re: ral(4) and wpa_supplicant?

[matthew sporleder <msporleder%gmail.com@localhost>]

On 5/25/09, Roy Marples <roy%marples.name@localhost> wrote:
> Geert Hendrickx wrote:
>
> > Not for me...  Instead of:
> >
> > Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447
> MHz)
> > ioctl[SIOCS80211, op 21, len 42]: Invalid argument
> > Association request to the driver failed
> >
> > I'm now getting:
> >
> > Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447
> MHz)
> > Associated with 00:22:b0:cf:6d:35
> > WPA: Could not verify EAPOL-Key MIC - dropping packet
> > WPA: Could not verify EAPOL-Key MIC - dropping packet
> > WPA: Could not verify EAPOL-Key MIC - dropping packet
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> >
> > (in a loop)
> >
>
>  Well that shows that the interface is has associated (which is what the
> patch fixed) and you now have a different error.
>
>  Try adding the wpa_supplicant -d flag to enable more debugging.
>  But I can't really help anymore as I don't know the actual guts of
> wireless.


For what it's worth I have a system with an ath and a ral on current
and ath can use wpa_supplicant just fine but ral loops in the
"Association request to the driver failed" message.  I haven't had a
chance to try wpa_supplicant from pkgsrc yet.