From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tamas Selmeci <tselmeci@dension.com>
Date: Tue, 25 Nov 2008 17:17:49 +0100
Subject: [ath9k-devel] 2.6.28-rc6: still can't set up AP mode
Message-ID: <492C252D.4080700@dension.com>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hello all!

Today I again made a try with ath9k from linux-2.6.28-rc6 (and of course 
with wireless-testing cloned on 24-Nov-2008)

I'm using hostapd-0.6.6 (configured with nl80211), iw-0.9.6 and libnl-1.1.

With ath9k the station mode operates perfectly with both Ath5416 and 
Ath9160. The problem is the AP mode. By default, ath9k refuses to switch 
to AP mode, I suppose it is still under heavy development... but a patch 
found on 
http://johannes.sipsolutions.net/patches/kernel/all/2008-10-28-08%3a33/ 
(008-allow-ap-vlan-modes.patch) makes is possible to switch to AP mode.

My hostapd configuration file is the following:
---------------------------------
interface=wlan0
driver=nl80211
hw_mode=g
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
ctrl_interface_group=0
macaddr_acl=0
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
dump_file=/tmp/hostapd.dump
wpa=3
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP
ssid=uwc_ap
wpa_psk=e757da617495f77f0a5b017c1d62eca6596adc36ab0955c5f6be7554b7a305d3
---------------------------------

And when running hostapd, it outputs:
---------------------------------
Configuration file: /tmp/dyncfg/hostapd.conf
Failed to update rate sets in kernel module
Failed to set CTS protect in kernel driver
Failed to set Short Slot Time option in kernel driver
Could not set preamble for kernel driver
Using interface wlan0 with hwaddr 00:1d:0f:b0:0e:ac and ssid 'uwc_ap'
Failed to set CTS protect in kernel driver
Failed to set Short Slot Time option in kernel driver
Could not set preamble for kernel driver
---------------------------------

Despite these, hostapd is still in the memory and running, but on my 
other PC the AP with the SSID can not be found.

My questions so far:
1) may I expect a working AP mode at the current state of ath9k? (I 
rememben formerly a few people reported that it works);
2) what am I doing wrong?
3) do I need CRDA? What is it good for at all (in a nuthsell) - links 
are also appreciated... The descriptions found in the tarball of CRDA 
and Linux wireless are not enough to make me understand what is it good 
for. I suspect that the lack of CRDA can cause that my new AP network 
cannot be seen.

Thanks,

Best regards,
-- 
Tamas Selmeci