Possible solution for "Failed to set PTK to the driver" errors with madwifi-ng

[Pieter Hollants]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just as a hint for other users, possibly those who like I work on
embedded systems: if wpa_supplicant on madwifi-ng based hardware fails
to complete its 4-way handshake with error messages such as these

WPA: Installing PTK to the driver.
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
ioctl[IEEE80211_IOCTL_SETKEY]: No such device or address.
WPA: Failed to set PTK to the driver.

then, as advanced users will immediately notice, this is not a
wpa_supplicant bug. And actually, it is no madwifi-ng bug either, as you
will find out if you use madwifi's 80211debug utility: error messages
like these appear when your system's module loading facilities do not
work properly. Unfortunately this error message is surpressed by default.

I thought this hint might be useful here, since users might probably not
be completely clear about the different components entailed, and the
same symptom might also occur with other drivers that employ the
net80211 stack.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGuCta8/cc5b1WpwRAkrvAJ9JPln7tqViDXPI4akWVtTfeRn2oACgpN52
7g+Tsc43GcKPWbzN3wW9It4=
=NNQm
-----END PGP SIGNATURE-----