• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Dreamplug, SD8787, AP, AccessPoint  (Read 2086 times)
ineiti
Newbie
*

Karma: 0
Posts: 2


View Profile
« on: November 25, 2013, 02:06:42 AM »

Trying to revive this thorny subject... Here is what I tried:

- u-boot from u-boot_2013.10-2_armel.deb
- 3.12.1-version of the kernel from http://www.xilka.com/
- the latest version of the sd8787-firmware (md5sum: bda543cb5943eac34e16d12911f3ee99)
- the latest version of hostapd from git

But there is definitively something wrong, as I only get a "mlan0"-interface, and no "wlan0" or other.

If I use mlan0 in hostapd, I get the following error:

Configuration file: hostapd.conf
ieee80211 phy0: mlan0: changing to 3 not supported
ieee80211 phy0: mlan0: changing to 3 not supported
nl80211: Could not configure driver mode
nl80211 driver initialization failed.
hostapd_free_hapd_data: Interface mlan0 wasn't started

Any idea what I missed? It works fine in client-mode, but I'd prefer AP Wink
Logged

debio
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #1 on: January 31, 2014, 09:54:54 PM »

I think our biggest source of problems is this:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/mwifiex?id=1211c961170cedb21c30d5bb7e2033c8720b38db

This was the commit that disabled the creation of the uap0 and ptp0 interfaces. The commit description claims these interfaces can be created manually through `iw`, but I haven't figured out how to create an AP mode interface.
Logged

debio
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #2 on: January 31, 2014, 10:34:34 PM »

I just reversed that commit and built a kernel image, and it looks like I have AP mode. Hostapd starts up on uap0. I'll have to test it to see if it's actually stable.

I guess the next step is probably to email Linux-wireless to complain that the mwifiex driver doesn't support changing an interface from managed mode to AP mode, but the iw utilities don't provide a way to create an AP mode interface.

Logged

debio
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #3 on: January 31, 2014, 10:55:27 PM »

Yes, AP mode works and I can connect. Throughput is pretty nice as well.

Then the card hung, the driver tried to reset it and failed to load the firmware after reset, and hostapd started panicking because the interface disappeared out from under it.

I'll see if I can tweak it at all.
Logged

debio
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #4 on: February 01, 2014, 09:38:58 PM »

I emailed Linux-wireless, and apparently we're supposed to create the AP interface with a command like this: `iw dev mlan0 interface add uap0 type __ap`
This should eliminate the need for any kernel patches.

The next problem I'm having is that after running the access point for a while, the interfaces transmit queue hangs. With WPA, it tends to happen within a few seconds or minutes. With no encryption, it lasts longer, but eventually hangs after tens of minutes or an hour or two. Are you seeing something similar?
Logged

debio
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #5 on: February 07, 2014, 08:16:50 PM »

I went ahead and opened a kernel bug at https://bugzilla.kernel.org/show_bug.cgi?id=70191 to try to investigate the instabilities.
Logged

alexK
Newbie
*

Karma: 1
Posts: 22


View Profile
« Reply #6 on: February 08, 2014, 04:45:28 PM »

I've been struggling with this problem as well.
I've got the following installed and working on my DreamPlug model: 003-DS2001:
wget http://http.debian.net/debian/pool/main/u/u-boot/u-boot_2012.04.01-2_armel.deb
wget http://http.debian.net/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/uImage
wget http://http.debian.net/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/uInitrd

It has the 8787 wifi chipset.

As suggested in a previous post, I tried:
root@shirati:/etc/apt# iw dev mlan0 interface add uap0 type __ap
command failed: No such device (-19)
root@shirati:/etc/apt#

but as you can see, I'm missing something.  The "__ap" looks suspicious.
I'd be grateful for any guidance.
cheers,alex
Logged

Pages: [1]
Print
Jump to: