caiwang
commented
9 years ago 
test on kernel 3.18 rock ubuntu image
Using iw to add a virtual wireless interface http://superuser.com/questions/592296/using-iw-to-add-a-virtual-wireless-interface-getting-the-error-no-such-device
root@radxa:/# iw dev wlan0 interface add wlan2 type managed
command failed: Operation not supported (-95)
root@radxa:/# iw phy phy0 interface add wlan2 type managed
command failed: Operation not supported (-95)
root@radxa:/# iw phy phy0 interface add wlan2 type monitor
command failed: Operation not supported (-95)
root@radxa:/# iw phy phy0 interface add wlan2 type
Usage: iw [options] phy
Add a new virtual interface with the given configuration. Valid interface types are: managed, ibss, monitor, mesh, wds.
The flags are only used for monitor interfaces, valid flags are: none: no special flags fcsfail: show frames with FCS errors control: show control frames otherbss: show frames from other BSSes cook: use cooked mode
The mesh_id is used only for mesh mode.
Options: --debug enable netlink debugging root@radxa:/#
root@radxa:/# iw --debug phy phy0 interface add wlan2 type monitor
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 48
.nlmsg_type = 20 <0x14>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1425439549
.nlmsg_pid = 1400
[PAYLOAD] 32 octets
07 00 00 00 08 00 01 00 00 00 00 00 0a 00 04 00 77 6c ................wl
61 6e 32 00 00 00 08 00 05 00 06 00 00 00 an2...........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 68
.nlmsg_type = 2
https://github.com/lwfinger/rtl8723au/issues/43
Probably not. The version of the driver that supports nl80211 commands is from the current kernel, and that code is what constitutes the kernel-version branch of this repo. It requires kernel 3.15, but it may build with 3.14.
I have no plans to update the main branch, and the kernel-version will just get the latest code copied from the kernel source. As the driver is now in the kernel, and that version supports cfg80211, I see no purpose in maintaining an older version. If you cannot use a new kernel, but want the latest driver for the rtl8723au, you will need to do the backport yourself. The Backports project will show you some of the things that need to be done.