<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hello,<br><br>"Trying to set up an Atheros mini WiFi PCI in mode AP using ath5k and hostapd"<br><br>In my previous mail I have given a full description about my configuration and I commented that I could not<br>execute hostapd. The problem was that I tried to build "hostapd" from the source code and I made some mistakes and then<br>I decided to install "hostapd" using apt-get (which is a good choice). So the problem is that when I was calling "hostapd" I was<br>executing the "wrong" executable instead of the executable installed using apt-get.<br><br>So, the summary to made work hostapd using the ath5k module provided by the kernel 2.6.31 is:<br>1) load the "ath5k" module which is included in the new kernel 2.6.31 (modprobe ath5k)<br>2) load he "hostap" module, which is also icluded in the new kernel 2.6.31 (modprobe hostap)<br>3) Install the the "hostapd" utility, version 0.6.9, which I have installed via "apt-get install hostapd".<br> I have used "deb http://ftp.es.debian.org/debian sid contrib non-free main" in the configuration file<br> "/etc/apt/sources.list" in order to install the latest version of hosapd; that is, 0.6.9<br>4) The basic configuration of the file "/etc/hostapd/hostapd.conf" is:<br> interface=wlan0<br> driver=nl80211<br> logger_syslog=-1<br> logger_syslog_level=2<br> logger_stdout=-1<br> logger_stdout_level=2<br> debug=4<br> dump_file=/tmp/hostapd.dump<br> ctrl_interface=/var/run/hostapd<br> ctrl_interface_group=0<br> hw_mode=g<br> ssid=ESSID_Genar<br> auth_algs=3<br> eapol_key_index_workaround=0<br> eap_server=0<br> channel=6<br><br>Notice that the driver used in configuration file is "driver=nl80211", which seems to be the suitable driver to be used<br>by all the "Linux mac80211 drivers" (for example the "ath5k" module has developed to be a "Linux mac80211 drivers",<br>like the driver "ath9k", which is suitalbe for 11n WiFi's).<br><br>In my case the information about the miniPCI Wi-Fi can be seen executing the command: lspci -vvv; that is:<br><br>00:0c.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)<br> Subsystem: Atheros Communications Inc. Compex Wireless 802.11 b/g MiniPCI Adapter, Rev A1 [WLM54G]<br> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-<br> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-<br> Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes<br> Interrupt: pin A routed to IRQ 9<br> Region 0: Memory at e0080000 (32-bit, non-prefetchable) [size=64K]<br> Capabilities: [44] Power Management version 2<br> Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)<br> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-<br> Kernel driver in use: ath5k<br> Kernel modules: ath5k<br><br>Note: Before loading the module "ath5k" there did not exist the line:<br> Kernel driver in use: ath5k<br> That is this line has appeared after executing: "modprobe ath5k"<br><br>Regards,<br><br> <br /><hr />Windows Live™: Keep your life in sync. <a href='http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009' target='_new'>Check it out!</a></body>
</html>