FS#33436 - [hostapd] New wersion fails to start

Attached to Project: Community Packages
Opened by Dario Bertero (Arthnr) - Friday, 18 January 2013, 13:29 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 29 January 2013, 13:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
with the new update to version 2.0, using the same configuration working before the update, hostapd does not start with this debug output (using -dd flag):
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
nl80211: interface wlan0 in phy phy0
rfkill: initial event: idx=0 type=5 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=4 op=0 soft=0 hard=0
rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=0
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: TDLS supported
nl80211: TDLS external setup
nl80211: Add own interface ifindex 3
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Setup AP - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x6b9290
nl80211: Register frame type=0xb0 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x0 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x20 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xa0 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xc0 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xd0 nl_handle=0x6b9290
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Failed to set interface wlan0 into AP mode
netlink: Operstate: linkmode=0, operstate=6
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211 driver initialization failed.


Additional info:
* Version 2.0


Steps to reproduce:
sudo hostapd -dd -B /etc/hostapd/hostapd.conf
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 29 January 2013, 13:15 GMT
Reason for closing:  Upstream
Additional comments about closing:  and probably kernel issue
Comment by Sergej Pupykin (sergej) - Monday, 21 January 2013, 08:50 GMT
Please post your config. I cannot reproduce it with dlink dwa-140 and WPA2 AP.
Comment by Dario Bertero (Arthnr) - Monday, 21 January 2013, 08:55 GMT
I did not use encription, nor DHCP.
   hostapd.conf (60.8 KiB)
Comment by Ivan (Nekroman) - Tuesday, 22 January 2013, 16:33 GMT
I can confirm this bug.
04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
Comment by Leonid Isaev (lisaev) - Wednesday, 23 January 2013, 17:58 GMT
First of all, I can't reproduce the issue with
05:05.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)
Subsystem: D-Link System Inc DWA-552 802.11n Xtreme N Desktop Adapter (rev A2)
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 20
Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath9k

As I said here (https://bbs.archlinux.org/viewtopic.php?pid=1220143) there seems to be an problem with hostapd 2.0 removing support for mon.xxx interface. Apparently, some drivers can't handle this on certain hardware. Those affected, could you please write to hostapd ML (http://lists.shmoo.com/mailman/listinfo/hostap)?

Loading...