On Friday 24 June 2016 03:16 PM, Jouni Malinen wrote:
On Thu, Jun 23, 2016 at 03:10:59PM +0000, Bob wrote:
No issue to start the AP alone with the minimal hostapd configuration
channel=6
hw_mode=g
but failed when virtual station is already up.
Which channel is the station interface using here? The driver is
unlikely to support multiple different channels, so that could be
behind the issue.
Then hostapd gives following errors
~~~
nl80211: send_mlme - da= ff:ff:ff:ff:ff:ff noack=0 freq=0 no_cck=0
offchanok=0 wait_time=0 fc=0xc0 (WLAN_FC_STYPE_DEAUTH) nlmode=3
nl80211: send_mlme -> send_frame
nl80211: send_frame - Use bss->freq=2412
nl80211: send_frame -> send_frame_cmd
nl80211: Frame command failed: ret=-16 (Device or resource busy)
(freq=2412 wait=0)
~~~~
That's not a real issue, i.e., that's fine to ignore. The real issue
would likely show up in the log either before or after this message.
Hello Jouni,
Thanks for the response. Good news is, everything is working after I
upgraded the system yesterday. Don't know, which software has fixed it,
but the hostapd version and configuration are still same. Only issue,
hostapd fails to run after ram hibernation. It shows
~~~
nl80211: Register frame command failed (type=176): ret=-114 (Operation
already in progress)
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Could not configure driver mode
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=13)
~~~~
further checking shows a hostapd process is already exist at background.
Killing the same fixed the issue.
What can be done to handle this during hibernation ?
regards,
Bob
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
