Grant schrieb: >> 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 >> > > Thanks a lot Norman. I've got to remember not to ride the bleeding > edge. Removing wlan0 from /etc/conf.d/hostapd didn't prevent hostapd > from starting it? > > - Grant > > Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as you wish hostapd to use wlan0. The init scripts are not able to set up master mode correctly and bring up an error or set up wlan0 interface in a false mode so hostapd can not set it up any more. So i set up my init to completely ignore wlan0 till hostapd handles it. Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i removed it completely. Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.
One thing,you might stumble accross later on. In hostapd.conf provide the wpa key in hex, not in phrase. phrase coused authentication errors for me an for one guy in the thread i talked about earlier. Otherwise the system runs fine and stable now. I hope there will be a less messy init-setting soon, as this functions get stabilized. Norman
