From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Javier Cardona <javier@cozybit.com>,
Steve Derosier <steve@cozybit.com>,
devel@lists.open80211s.org
Subject: Re: [RFC 5/5] cfg80211/mac80211: add mesh join/leave commands
Date: Wed, 01 Dec 2010 22:15:29 +0100 [thread overview]
Message-ID: <1291238129.4199.18.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20101201210226.159495600@sipsolutions.net>
On Wed, 2010-12-01 at 21:59 +0100, Johannes Berg wrote:
> plain text document attachment (022-cfg80211-start-stop-mesh.patch)
> From: Johannes Berg <johannes.berg@intel.com>
>
> Instead of tying mesh activity to interface up,
> add join and leave commands for mesh. Since we
> must be backward compatible, let cfg80211 handle
> joining a mesh if a mesh ID was pre-configured
> when the device goes up.
>
> Note that this therefore must modify mac80211 as
> well since mac80211 needs to lose the logic to
> start the mesh on interface up.
I just noticed that this will lose mesh parameters when you leave the
mesh, unlike previously where they would be kept. I'm not sure which
behaviour is more desirable though -- if I was doing this from scratch
I'd sure go with the reset behaviour, but we may need to keep the old
behaviour?
johannes
next prev parent reply other threads:[~2010-12-01 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 20:59 [RFC 0/5] mesh join/leave API Johannes Berg
2010-12-01 20:59 ` [RFC 1/5] mac80211: use configured mesh TTL Johannes Berg
2010-12-01 20:59 ` [RFC 2/5] mac80211: move mesh filter adjusting Johannes Berg
2010-12-01 20:59 ` [RFC 3/5] cfg80211: require add_virtual_intf to return new dev Johannes Berg
2010-12-01 20:59 ` [RFC 4/5] nl80211: refactor mesh parameter parsing Johannes Berg
2010-12-02 8:34 ` [RFC 4/5 v2] " Johannes Berg
2010-12-01 20:59 ` [RFC 5/5] cfg80211/mac80211: add mesh join/leave commands Johannes Berg
2010-12-01 21:15 ` Johannes Berg [this message]
2010-12-02 0:23 ` Javier Cardona
2010-12-02 6:57 ` Johannes Berg
2010-12-02 8:45 ` [RFC 5/5 v2] " Johannes Berg
2010-12-02 20:09 ` Javier Cardona
2010-12-02 20:14 ` Johannes Berg
2010-12-02 21:24 ` Javier Cardona
2010-12-02 21:38 ` Johannes Berg
2010-12-02 23:08 ` Javier Cardona
2010-12-03 8:13 ` 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=1291238129.4199.18.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--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).