hostapd version 0.6.7 and 0.6.8 fail to work with madwifi-ng-0.9.4 in wpa/wpa2 mode, giving the following message a couple of times on hostapd startup: ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument If you google around this ioctl failure is reported upstream for wpa_supplicant and madwifi-ng in several cases (didn't try wpa_supplicant since i'm using these boards for master mode).
Created attachment 183250 [details] emerge --info
Created attachment 183252 [details] hostapd.conf with (obviously) modified ssid/psk
Versions are all stable: net-wireless/madwifi-ng-0.9.4 sys-kernel/linux-headers-2.6.27-r2 net-wireless/hostapd-0.5.10 works just fine in two different machines with everything stable. ath_pci is set to autocreate=ap also.
Is there a chance that you can give it a try with gentoo-sources-2.6.28-r2 (~x86 keyworded) and see if that helps?
Yes, i can give it a spin in a couple of hours and i'll report back here then.
Created attachment 183271 [details] hostapd-0.6.8 -dd log output w/2.6.28-gentoo-r2 hostapd-0.6.8 + gentoo-sources-2.6.28-r2 seems to work even though it still spits the error (though the service starts correctly other than noisy). If i use wpa=1 (WPA only) it works fine, using wpa=2 or wpa=3 (WPA2 only or WPA+WPA2) it fails, but this failed on 0.5.10 too so it's not a regression (probably some bad madwifi-ng mojo in master mode).
Ok found the problem wrt to WPA2. See http://lists.shmoo.com/pipermail/hostap/2007-July/016011.html Solution: add einfo in the hostap ebuild for madwifi users to disable wme (comment out wme_enabled=1 or set it to 0, default in shipped config is enabled) or conditionally do so on USE=madwifi (i wouldn't recommend this). Tested clients: linux-arm w/zd1211rw and osx-ppc with builtin (b43).
I've added a warning regarding madwifi and wme_enabled to the postinfo of the ebuild. I'm closing this bug, since it is fixed.
