From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] single radio routers and ap/adhoc interfaces
Date: Wed, 26 Jun 2013 21:01:17 +0200 [thread overview]
Message-ID: <20130626190117.GF2120@ritirata.org> (raw)
In-Reply-To: <CAKON4OzQpsZdGFoEPDpsZcCyu0pGBWLpuNoQZkgcYX-7CmzKqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
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,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-26 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 17:30 [B.A.T.M.A.N.] single radio routers and ap/adhoc interfaces jonsmirl
2013-06-26 18:02 ` Antonio Quartulli
2013-06-26 18:18 ` Steve Song
2013-06-26 18:36 ` jonsmirl
2013-06-26 18:45 ` Antonio Quartulli
2013-06-26 18:49 ` Steve Song
2013-06-26 18:56 ` jonsmirl
2013-06-26 19:01 ` Antonio Quartulli [this message]
2013-06-26 20:21 ` jonsmirl
2013-06-26 19:02 ` jonsmirl
2013-06-26 18:38 ` jonsmirl
2013-06-26 18:46 ` Antonio Quartulli
2013-06-26 21:45 ` cmsv
2013-06-26 22:39 ` jonsmirl
2013-06-26 22:59 ` Gui Iribarren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130626190117.GF2120@ritirata.org \
--to=ordex@autistici.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox