Grant schrieb: > The madwifi/ath5k guys say it should work in 2.6.28 which I'm on. The > latest is I'm getting this directly from hostapd: > > Failed to set interface ath0 to master mode. > nl80211 driver initialization failed. > rmdir[ctrl_interface]: No such file or directory > ELOOP: remaining socket: sock=5 eloop_data=... > > I'm sure my procedure is correct now, but I don't know why ath0 won't > go into master mode. > > - Grant > > >
Hi, i have been, through that lately an it is not that out of the box. Here is what i put together from linux-wireless mailinglist and trial and error: 1. Master mode on ath5k is there, but not activated and not in 2.6.28. Mainly from this thread i got the kernel stuff and settings http://marc.info/?t=122652720700004&r=1&w=2 I use the latest git pull from http://linuxwireless.org/. The AP mode needs still to be activated: --- wireless-testing/drivers/net/wireless/ath5k/base.c 2009-02-10 06:11:43.186470883 +0100 +++ wireless-testing/drivers/net/wireless/ath5k/base.c.old 2008-11-14 09:36:40.000000000 +0100 @@ -522,6 +501,7 @@ hw->wiphy->interface_modes = BIT(NL80211_IFTYPE_STATION) | BIT(NL80211_IFTYPE_ADHOC) | + BIT(NL80211_IFTYPE_AP) | BIT(NL80211_IFTYPE_MESH_POINT); hw->extra_tx_headroom = 2; Now you have a kernel and a ath5k module capable of master mode. 2. You need ~arch version of hostapd. Stable version did not do the trick for me. 3. I needed to modify the startscripts. I removed the net.wlan0 link completely, as it does not seem to be able to initialize the ap mode, but is loaded automaticaly even when it is not set to boot in a spezific runlevel. So you need hostapd to initialize the wlan-nic. hostapd script wants to start all networkinterfaces with the rc-scripts, so i edited the script, to start my bridge an the wired card only and leave out the wlan-nic. I think this is a little redundant to removing the net.wlan0 script. Sometimes while testing, the interface did not shut down properly and hostapd could not initialize them any more. So i had to set them down manually with iwconfig. After that hostapd could use them again. This is clearly not yet meant to be used in a productive environment, as the devs clearly stated in the postet threads on wireless-linux. Regards, Norman
