Jumpnow Technologies

home code consulting contact

Duovero Access Point

14 Jan 2014

The Gumstix Duovero Zephyr come with a built-in combination wifi/bluetooth radio.

The wifi radio supports operating as an access point.

The Duovero Zephyr uses a Marvell SD8787 radio attached to the SDIO bus.

The mwifiex and mwifiex_sdio modules are available in Linux 3.6 which is the default kernel for the Duovero boards.

The Marvell drivers require the sd8787_uapsta.bin binary firmware.

When you boot a Duovero with these drivers included you’ll get two wireless interfaces, mlan0 and uap0.

The mlan0 interface is used for client managed and ad-hoc mode connections.

The uap0 interface is for access point mode.

#### Note

With commit d82b49b Gumstix disabled the uap0 interface from their Duovero kernels. You will need to remove this patch from your kernel recipe if you are using meta-gumstix or you can use the meta-duovero layer described below.

The system should look something like this running on a Gumstix Parlor expansion board

root@duovero:~# ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:15:C9:28:F8:95
      inet addr:  Bcast:  Mask:
      inet6 addr: fe80::215:c9ff:fe28:f895/64 Scope:Link
      RX packets:103091 errors:0 dropped:2 overruns:0 frame:0
      TX packets:5352 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:12879802 (12.2 MiB)  TX bytes:564902 (551.6 KiB)

lo    Link encap:Local Loopback
      inet addr:  Mask:
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:16436  Metric:1
      RX packets:37 errors:0 dropped:0 overruns:0 frame:0
      TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:11880 (11.6 KiB)  TX bytes:11880 (11.6 KiB)

mlan0 Link encap:Ethernet  HWaddr 00:19:88:24:FB:9C
      BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

uap0  Link encap:Ethernet  HWaddr 00:19:88:24:FB:9C
      inet addr:  Bcast:  Mask:
      inet6 addr: fe80::219:88ff:fe24:fb9c/64 Scope:Link
      RX packets:587 errors:0 dropped:0 overruns:0 frame:0
      TX packets:539 errors:25 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:152279 (148.7 KiB)  TX bytes:84038 (82.0 KiB)

You can check the firmware version by looking at the boot log

root@duovero:~# dmesg | grep mwifiex
[    4.902313] mwifiex_sdio mmc1:0001:1: WLAN FW is active
[    5.193237] mwifiex_sdio mmc1:0001:1: driver_version = mwifiex 1.0 (14.66.9.p96)

The standard Linux software for access point management is hostapd.

I’m using the [dizzy] branch of Yocto to build the Duovero system. Instructions are here. There is a recipe for hostapd v1.0 in the meta-openembedded repo called hostap-daemon, but it doesn’t work with the Duovero.

I have new recipe for a more recent hostapd v2.3 build in the meta-duovero layer. I did have to back out one patch to the hostapd source to get it to work with the Duovero.

You can find the recipe with patch here.

If you want a full Duovero rootfs image recipe, you can use this console-image.bb. It includes some useful AP tools like a dhcp server and the iptables utility.

If you just want to try out some binaries, you can find them at jumpnowtek.com/downloads/duovero.


You will need to customize a few configuration files for your own use.

uap0 - /etc/network/interfaces

In the /etc/network/interfaces file, you need to configure the uap0 interface. I you uncomment the example already there, uap0 will have an IP address of

--- /etc/network/interfaces ---
### access point interface
auto uap0
iface uap0 inet static

hostapd - /etc/hostapd.conf

The hostapd configuration file is /etc/hostapd.conf. There is a simple WPA/WPA2 example that you can modify.

--- /etc/hostapd.conf ---

Replace the values for ssid and wpa_passphrase. The wpa_passphrase has to be at least 8 characters long.

To create an open access point, you could use an even simpler configuration like this

--- /etc/hostapd.conf ---

An explanation for all of the hostapd.conf options can be found here - hostapd.conf.

hostapd - /etc/default/hostapd

You also need to enable the hostapd daemon in the /etc/default/hostapd configuration file.

--- /etc/default/hostapd ---

Change the HOSTAPD_ENABLE value to yes.

dhcpd - /etc/dhcp/dhcpd.conf

You probably want the access point to give out dhcp addresses. There is a dhcp server installed in the console-image.

The main configuration file is /etc/dhcp/dhcpd.conf. The provided example assumes the address for uap0.

--- /etc/dhcp/dhcpd.conf

ddns-update-style none;
option domain-name "jumpnow";
option domain-name-servers;

# make uap0 the gateway for clients
option routers;

default-lease-time 600;
max-lease-time 7200;

subnet netmask {

This example configuration will give out addresses in the range -

dhcpd - /etc/default/dhcp-server

Here you need to specify the interface the dhcp server should listen on.

--- /etc/default/dhcp-server

After making all of the configuration changes, you can restart the systems manually.

This will stop the applicable services

root@duovero# /etc/init.d/dhcp-server stop
root@duovero# /etc/init.d/hostapd stop
root@duovero# ifdown uap0

This will start the services

root@duovero# ifup uap0
root@duovero# /etc/init.d/hostapd start
root@duovero# /etc/init.d/dhcp-server start

Or you can just reboot.

You should now be able to connect to the Duovero access point with a client. You should get an IP address from the dhcp server.

From the client you should be able to ssh into the access point at or whatever address you gave uap0.


— This section is still a work in progress. —

I enabled some basic netfilter modules in the kernel. Enough so that I could
do some basic NAT routing

The first thing is to enable packet forwarding in the kernel

root@duovero:~# sysctl -w net.ipv4.ip_forward=1

To make this permanent uncomment this line in /etc/sysctl.conf

--- /etc/sysctl.conf ---
# Uncomment the next line to enable packet forwarding for IPv4

Load the iptable_nat kernel module

root@duovero:~# modprobe iptable_nat
[ 2109.500854] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2109.516845] nf_conntrack version 0.5.0 (15836 buckets, 63344 max)

To have this kernel module load at boot

root@duovero:~# echo iptable_nat > /etc/modules

Add a basic NAT routing rule using the eth0 interface

root@duovero:~# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

After that clients using the Duovero AP should be able to see the network that eth0 is attached to and browse the Internet if a valid nameserver was given out by the Duovero dhcp server.

TODO: Add a script to load firewall rules at startup

Client Isolation

I connected some more clients to the Duovero AP. They could all communicate fine with the AP, but they could not talk to each other.

This is probably intentional wireless client isolation by the mwifiex driver or Marvell firmware. Some additional routing would need to be done by the Duovero in order to support client-to-client communication.

Max Clients

A user on the Gumstix Mailing List posted that 10 clients was the maximum the AP driver was accepting. I have not verified.


This is a pretty simple access point implementation, but it should be enough to get a project started.