Problems starting hostapd 2.0

[Antonio Toma]

The two logs exceeded the mailing list message size limit, but I'll
report here the starting sequences from both

#### Start Log Hostapd 2.0
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=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 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 0x1b84ba0
nl80211: Register frame type=0xb0 nl_handle=0x1b84ba0
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x0 nl_handle=0x1b84ba0
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0x20 nl_handle=0x1b84ba0
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xa0 nl_handle=0x1b84ba0
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xc0 nl_handle=0x1b84ba0
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Register frame type=0xd0 nl_handle=0x1b84ba0
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.
#### End Log Hostapd 2.0

while the corresponding section in the log of hostapd 1.1 looked like

#### Start Log Hostapd 1.1
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=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 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: Register frame command failed (type=208): ret=-114 (Operation
already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Failed to register Action frame processing - ignore for now
nl80211: Add own interface ifindex 3
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Create interface iftype 6 (MONITOR)
nl80211: New interface mon.wlan0 created: ifindex=6
nl80211: Add own interface ifindex 6
#### End Log Hostapd 1.1

With major differences after 'TDLS'.
So the 'Register frame command failed' is present in both cases, but
the effect is quite different.

Does this help in analysis?

Regards.
Antonio.


On 2/1/13, Antonio Toma <antonio.toma at gmail.com> wrote:
> Hi Mihai,
>
> here is the log information.
> I'm not able to attach a log including a STA connection since my
> problem is indeed that hostapd 2.0 won't start, so I attach the failed
> start for hostapd 2.0 and the one for successfully starting hostapd
> 1.1.
>
> Hope it helps.
>
> Antonio.
>
> On 1/31/13, Antonio Toma <antonio.toma at gmail.com> wrote:
>> Hi Mihai,
>>
>> I'm running kernel 3.7.5 but I was on 3.6.11 when I first tried to
>> upgrade to hostapd 2.0 (and failed).
>> I'll provide you the log info as soon as I get my hands back on the
>> machine.
>>
>> Regards.
>> Antonio.
>>
>> On 1/29/13, Mihai Moldovan <ionic at ionic.de> wrote:
>>> * On 29.01.2013 10:02 AM, Antonio Toma wrote:
>>>> I'm facing problems trying to upgrade from hostapd 1.1 to 2.0 in
>>>> ArchLinux.
>>>> The daemon fails to start using the same configuration that used to
>>>> work for (and still works if I downgrade to) 1.1
>>> What kernel version are you using? Can you please send me the debug log
>>> created with
>>> hostapd -dd /path/to/config
>>> ?
>>>
>>> Compressed or uncompressed, I don't mind. Start up hostapd, then have
>>> one
>>> STA
>>> trying to connect and once it says "authentication failed", or something
>>> along
>>> those lines, then terminate hostapd.
>>> However, don't necessarily post the file to the list, as there is a
>>> 25kbyte
>>> message size limit...
>>>
>>> You may be facing the same problems I do (and have backtraced to a
>>> specific
>>> kernel commit):
>>> http://lists.shmoo.com/pipermail/hostap/2013-January/027197.html
>>>
>>> Knowing your kernel version, I can create a patch to revert this commit
>>> and
>>> hopefully make hostapd work again.
>>>
>>> Best regards,
>>>
>>>
>>>
>>> Mihai
>>>
>>>
>>
>