I am trying to bridge a Bluetooth/Bluez PAN network with a WiFi
network on a gumstix connex 400xm-bt+wifistix-CF system. However, I am
unable to do this. The gumstix is a PAN NAP (Network Access Point) in
my set up and I have created a bridge on the gumstix that bridges the
bluez IP network interface (bnep0) and the wifi interface (mwlan0). I
have a PANU device that successfully connects to the gumstix over
bluetooth and another wifi device that connects to the gumstix over
After setting everything up, my PANU device can ping the gumstix over
the PAN network and vice versa. My wifi device can also ping the
gumstix and vice versa. However, when I try pinging from my PANU
device to my wifi device (or vice versa) it never works. I have been
able to replicate the exact set up with another ubuntu linux machine
that has BT+WiFi, in this setup the ubuntu machine replaces the
gumstix and acts as the bridge. Everything works as expected in this
Does anyone have any experience with this for the gumstix? Any
ideas/pointers would be appreciated.
If I set up a PAN network with the gumstix as the PAN gateway and 2
other PANU devices, everything works fine as expected. The problem
happens only when I try to do Bluetooth-WiFi bridging on the gumstix.
Investigating this problem has revealed that on the gumstix it seems
that the wifi interface does not go into the promiscuous mode that is
needed for wifi bridging to work. For instance I tried running tcpdump
on the gumstix for the mwlan0 interface and packets were captured only
when the mwlan0 MAC address was either the source or destination. In
scenarios where mwlan0's MAC address is not the source or destination,
I donot see any traffic being captured on the gumstix. tcpdump puts
the interface in promiscuous mode in order to capture all the traffic
on the interface and also prints a message on the console about this.
When running tcpdump for mwlan0 I donot see the message and traffic is
not captured. This leads me to believe that mwlan0 is not going into
promiscuous mode. e.g. if I run tcpdump for the usb0 interface, I see
a message on the console saying that usb0 was put into promiscuous
Can anyone confirm whether or not the mwlan0 interface can be put in
promiscuous mode? If this is not possible, is this a limitation in the
linux device driver or the Marvell chipset? Is there any way to enable
promiscuous mode for the mwlan0 interface/Marvell chipset?
Would appreciate any help regarding this.