linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 20:35:51 +0100	[thread overview]
Message-ID: <1291232151.4199.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1291229642.4199.11.camel@jlt3.sipsolutions.net>

On Wed, 2010-12-01 at 19:54 +0100, Johannes Berg wrote:

> If we had a 'start mesh' command, like 'join IBSS', then it'd be natural
> to have just more attributes in it. Maybe it's time to start thinking
> about that again, although backward compatibility could be interesting.

Ok I started looking at this ...

I have a feeling I asked this before, but can't remember -- is it
necessary to be able to change the mesh config on the fly, while the
mesh is active?

johannes


  reply	other threads:[~2010-12-01 19:35 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 [this message]
2010-12-01 20:09         ` Javier Cardona
2010-12-01 20:19           ` Johannes Berg
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=1291232151.4199.12.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).