<div text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
Using an Atheros AR5001X I manage to get hostapd working. It creates
a virtual monitor device and it can receive and send layer 2
packets. However, if I use an Intel NIC it fails to initiate. It is
looking for wlan0 interface but the wireless interface is identified
with eth1.<br>
<br>
Intel PRO/Wireless 2200BG output:<br>
<br>
<small>"Configuration file: hostapd.conf<br>
ctrl_interface_group=0<br>
nl80211: Register Action command failed: ret=-19 (No such device)<br>
nl80211: Register Action match - hexdump(len=1): 06<br>
nl80211: Failed to register Action frame processing - ignore for
now<br>
nl80211: Add own interface ifindex 0<br>
Could not read interface wlan0 flags: No such device<br>
nl80211 driver initialization failed.<br>
ELOOP: remaining socket: sock=4 eloop_data=0x8f27878
user_data=0x8f29580 handler=0x8073aa0<br>
ELOOP: remaining socket: sock=6 eloop_data=0x8f2ad20
user_data=(nil) handler=0x807d360"<br>
<big><br>
Other thing, is that using Atheros NIC it only receive Probe
Request and send Probe Responses. Why aren't beacon frames being
processed? At configuration file everything seems ok to me.<br>
<br>
Thanks,<br>
Carlos</big><br>
</small><br>
On 02/25/2011 12:21 PM, Jouni Malinen wrote:
<blockquote type="cite">
<pre>On Fri, Feb 25, 2011 at 10:31:47AM +0000, Carlos Guimarães wrote:
</pre>
<blockquote type="cite">
<pre>I would like to know if my NIC must be in monitor mode so that I can run
hostapd correctly.
</pre>
</blockquote>
<pre>No, there is no such requirement. In general, hostapd tries to set up
the driver in suitable mode when starting up AP functionality.
</pre>
</blockquote>
<br>
</div>