From: Javier Cardona <javier@cozybit.com>
To: Simon Raffeiner <sturmflut@lieberbiber.de>
Cc: Andrey Yurovsky <andrey@cozybit.com>,
Johannes Berg <johannes@sipsolutions.net>,
Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: allow adding new station to devices in mesh mode
Date: Mon, 8 Feb 2010 09:26:05 -0800 [thread overview]
Message-ID: <445f43ac1002080926y4912fa6n7d94ce3333e879f5@mail.gmail.com> (raw)
In-Reply-To: <201002081454.13561.sturmflut@lieberbiber.de>
Simon,
On Mon, Feb 8, 2010 at 5:54 AM, Simon Raffeiner
<sturmflut@lieberbiber.de> wrote:
> Am Sonntag 07 Februar 2010 08:51:03 pm schrieben Sie:
>
>> It was supported for automated testing and experimentation (you could
>> then force certain topologies).
>
> Wouldn't one have to disable beaconing then, or at least automatic peering? IMO you can't force a topology if the nodes are still beaconing and establishing paths at the same time.
Automatic peering can be disabled via NL80211_MESHCONF_AUTO_OPEN_PLINKS.
Javier
--
Javier Cardona
cozybit Inc.
http://www.cozybit.com
prev parent reply other threads:[~2010-02-08 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 1:00 [PATCH] nl80211: allow adding new station to devices in mesh mode Thadeu Lima de Souza Cascardo
2010-02-05 9:39 ` Johannes Berg
2010-02-05 9:59 ` Johannes Berg
2010-02-05 16:57 ` Thadeu Lima de Souza Cascardo
2010-02-05 17:47 ` Andrey Yurovsky
2010-02-05 17:55 ` Thadeu Lima de Souza Cascardo
2010-02-05 19:04 ` Simon Raffeiner
2010-02-05 23:16 ` Andrey Yurovsky
2010-02-06 8:59 ` Johannes Berg
2010-02-07 19:51 ` Andrey Yurovsky
2010-02-08 9:08 ` Johannes Berg
2010-02-08 19:25 ` Javier Cardona
2010-02-08 20:26 ` Thadeu Lima de Souza Cascardo
2010-02-09 7:58 ` Johannes Berg
2010-02-08 13:54 ` Simon Raffeiner
2010-02-08 17:26 ` Javier Cardona [this message]
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=445f43ac1002080926y4912fa6n7d94ce3333e879f5@mail.gmail.com \
--to=javier@cozybit.com \
--cc=andrey@cozybit.com \
--cc=cascardo@holoscopio.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sturmflut@lieberbiber.de \
/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