On Wed, Jun 26, 2013 at 02:56:06PM -0400, jonsmirl@gmail.com wrote:
On Wed, Jun 26, 2013 at 2:49 PM, Steve Song steve@villagetelco.org wrote:
We use a stock AA OpenWRT distribution (RC1 currently I think). All modifications to it are contained in the Github repo at https://github.com/villagetelco/vt-firmware We have instructions on setting up a build environment at http://wiki.villagetelco.org/How_To_Set_Up_a_SECN_Build_Environment
Maybe it has gotten broken in OpenWRT trunk. There was a large backport recently added to the kernel tree.
When I active the alternate interfaces they won't let the other one come up.
root@OpenWrt:/etc/config# root@OpenWrt:/etc/config# ifconfig ap0 up ifconfig: SIOCSIFFLAGS: Device or resource busy root@OpenWrt:/etc/config# root@OpenWrt:/etc/config# ifconfig adhoc0 down [ 2510.510000] batman_adv: bat0: Interface deactivated: adhoc0 root@OpenWrt:/etc/config# ifconfig ap0 up root@OpenWrt:/etc/config# ifconfig adhoc0 up ifconfig: SIOCSIFFLAGS: Device or resource busy root@OpenWrt:/etc/config#
In my 'iw phy' output:
valid interface combinations:
- #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO }
<= 8, #{ IBSS } <= 1, total <= 2048, #channels <= 1, STA/AP BI must match
- #{ AP } <= 1, total <= 1, #channels <= 1, STA/AP BI must match, radar detect
widths: { 20 MHz (no HT), 20 MHz }
How do you interpret this? It this saying one IBSS plus up to eight AP?
Seems so. Maybe you should directly ask on the openwrt mailing list/channel? They may know what to do.
Cheers,