From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Steve Derosier <steve@cozybit.com>,
devel@lists.open80211s.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Support beacon configuration via nl80211 for mesh interfaces
Date: Wed, 01 Dec 2010 21:19:11 +0100 [thread overview]
Message-ID: <1291234751.4199.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTimgfRvqp=-CDU=G8o-ZfD4fVbf3j-AdXCVtoM6c@mail.gmail.com>
On Wed, 2010-12-01 at 12:09 -0800, Javier Cardona wrote:
> It is convenient to be able to change things like the ttl or the auto
> peering without having to bring down the interface. People might also
> want to tune from userspace the different mesh timeouts in response to
> changes in operating conditions (e.g. mesh density).
Makes sense.
> But right now the only parameter that needs the mesh to be active is
> plink_action: one can only block or manually initiate peering after a
> beacon has been received from a suitable neighbor.
It looks like one can modify the mesh ID on the fly right now -- that
I'm going to remove, the other things can stay for all I care :-)
johannes
next prev parent reply other threads:[~2010-12-01 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 1:58 [PATCH] mac80211: Support beacon configuration via nl80211 for mesh interfaces Javier Cardona
2010-12-01 6:19 ` Johannes Berg
2010-12-01 18:45 ` Javier Cardona
2010-12-01 18:54 ` Johannes Berg
2010-12-01 19:35 ` Johannes Berg
2010-12-01 20:09 ` Javier Cardona
2010-12-01 20:19 ` Johannes Berg [this message]
2010-12-01 20:28 ` [PATCH/RFC] mac80211: use configured mesh TTL Johannes Berg
2010-12-01 20:32 ` [PATCH/RFC v2] " Johannes Berg
2010-12-01 20:44 ` [PATCH/RFC] " Javier Cardona
2010-12-01 20:51 ` Johannes Berg
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=1291234751.4199.13.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=steve@cozybit.com \
/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;
as well as URLs for NNTP newsgroup(s).