From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Cannot bring up second VAP on recent kernels?
Date: Mon, 22 Oct 2012 13:20:08 -0700 [thread overview]
Message-ID: <5085AA78.1080809@candelatech.com> (raw)
Anyone successfully using more than one virtual AP on
3.3 or higher kernels? It works fine for me on 3.0.32,
but my 3.3.8 and 3.5.7 kernels (and a few similar ones)
all fail with errors like this below:
Hardware is ath9k 3x3 9380 NIC.
[root@lec2010-ath9k-1 wifi]# cat hostapd_log_vap1.txt
1350936424.890962: random: Trying to read entropy from /dev/random
1350936424.891172: Configuration file: wifi/hostapd_vap1.conf
1350936424.892827: ctrl_interface_group=0
1350936424.895084: nl80211: interface vap1 in phy wiphy0
1350936424.895175: rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
1350936424.895456: nl80211: Using driver-based off-channel TX
1350936424.895483: nl80211: TDLS supported
1350936424.895500: nl80211: TDLS external setup
1350936424.895612: nl80211: Add own interface ifindex 26
1350936424.896560: nl80211: Set mode ifindex 26 iftype 3 (AP)
1350936424.896919: nl80211: Setup AP - device_ap_sme=0 use_monitor=0
1350936424.896992: nl80211: Subscribe to mgmt frames with AP handle 0x81e8910
1350936424.897018: nl80211: Register frame type=0xb0 nl_handle=0x81e8910
1350936424.897036: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897107: nl80211: Register frame type=0x0 nl_handle=0x81e8910
1350936424.897127: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897174: nl80211: Register frame type=0x20 nl_handle=0x81e8910
1350936424.897195: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897240: nl80211: Register frame type=0xa0 nl_handle=0x81e8910
1350936424.897261: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897306: nl80211: Register frame type=0xc0 nl_handle=0x81e8910
1350936424.897326: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897372: nl80211: Register frame type=0xd0 nl_handle=0x81e8910
1350936424.897392: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897438: nl80211: Register frame type=0x40 nl_handle=0x81e8910
1350936424.897458: nl80211: Register frame match - hexdump(len=0): [NULL]
1350936424.897681: nl80211: Register beacons command failed: ret=-16 (Device or resource busy)
1350936424.897830: nl80211: Failed to set interface vap1 into AP mode
1350936424.901888: netlink: Operstate: linkmode=0, operstate=6
1350936424.901996: nl80211: Set mode ifindex 26 iftype 2 (STATION)
1350936424.902197: nl80211 driver initialization failed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2012-10-22 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 20:20 Ben Greear [this message]
2012-10-22 21:19 ` Cannot bring up second VAP on recent kernels? Felix Fietkau
2012-10-22 21:26 ` Ben Greear
2012-10-22 21:45 ` Felix Fietkau
2012-10-22 22:52 ` Ben Greear
2012-10-22 23:27 ` Ben Greear
2012-10-23 7:21 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5085AA78.1080809@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).