Search Linux Wireless

Fwd: mwifiex and SD8787: How to create AP interface?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Avinash,

Thanks! That works for me. Would it be possible to add this to the
mwifiex page on wireless.kernel.org? As far as I know, this command is
completely undocumented within iw, and I know I'm not the only
Dreamplug owner experiencing this problem.

As for other issues, I'm seeing a hang in the TX queue on the device
after running an AP for a while, but I'm still gathering information
on that. I'll follow up with another thread.

Thanks,
Andrew

On Sat, Feb 1, 2014 at 9:48 PM, Avinash Patil <avinashapatil@xxxxxxxxx> wrote:
> Hi Andrew,
>
> AP interface can be created using iw utility. Command is as follows:
>
> iw dev mlan0 interface add uap0 type __ap
>
> There onwards hostapd can be used to start mwifiex AP operations. Please let
> me know if you face any issues.
>
> Thanks,
> Avinashw
>
> On Feb 2, 2014 8:28 AM, "Andrew Wiley" <wiley.andrew.j@xxxxxxxxx> wrote:
>>
>> Hello linux-wireless,
>>
>> I'm trying to get AP mode to work on a Marvell Kirkwood-based
>> Dreamplug with an SD8787 SDIO wireless chipset.
>>
>> Originally, the mwifiex driver would create three interfaces when it
>> loaded - mlan0, uap0, and ptp0, for station mode, AP mode, and PTP
>> mode, respectively. That behavior was removed in commit 1211c (
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/mwifiex?id=1211c961170cedb21c30d5bb7e2033c8720b38db
>> ) because NetworkManager was trying to use all of the interfaces
>> rather than just mlan0.
>>
>> As I understand it, the normal workflow for this is that hostapd
>> changes an interface from station mode to AP mode when it starts up,
>> but when it tries to do this on the mlan0 interface, nl80211 returns
>> Operation Not Supported. Depending on the version of hostapd, it
>> either bails out there or tries to continue and bails out later in
>> setup.
>>
>> If I revert the patch I linked above, the driver creates the uap0
>> interface and I can run an AP with hostapd (although it has some other
>> issues - more on that in a later post).
>>
>> What is the "correct" way to access AP mode with this driver? As far
>> as I'm aware, there are no userspace utilities to directly create an
>> AP-mode interface, and mwifiex doesn't seem to support the normal
>> workflow that hostapd is trying to do.
>>
>> Thanks,
>> Andrew
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
>> in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux