All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: [PATCH] cfg80211: allow the plink state blocking for user managed mesh
Date: Fri, 17 Apr 2015 13:21:26 +0200	[thread overview]
Message-ID: <1429269686.1885.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAEFj986ZH3mUMNR8O_kzrBhQA2ozFKav46Enc6ru4JUTX=qC7g@mail.gmail.com> (sfid-20150416_115328_531730_F5482B5A)

On Thu, 2015-04-16 at 17:53 +0800, Yeoh Chun-Yeow wrote:
> On Thu, Apr 16, 2015 at 5:24 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2015-04-16 at 13:15 +0800, Chun-Yeow Yeoh wrote:
> >> User managed peering has no way to block the plink state
> >> for mesh peering setup by wpa_supp or authsae. Try to do
> >> allow this in kernel space, so that we can use iw utility
> >> to do that.
> >
> > I have no idea what you're trying to say here.
> >
> 
> wpa_supplicant and authsae allows us to do mesh peering in user space,
> but the plink state is still managed in kernel space.
> 
> But AFAIK, there is no implementation by wpa_supplicant or authsae to
> block the plink state.
> 
> By applying this patch, we can use the "iw mesh0 station set
> xx:xx:xx:xx:xx:xx plink_action block" to block the peer mesh STA. This
> is useful for experimenting purposes.

Can you please respin with a bit more detail in the commit log?

Thanks.

johannes


      reply	other threads:[~2015-04-17 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16  5:15 [PATCH] cfg80211: allow the plink state blocking for user managed mesh Chun-Yeow Yeoh
2015-04-16  9:24 ` Johannes Berg
2015-04-16  9:53   ` Yeoh Chun-Yeow
2015-04-17 11:21     ` Johannes Berg [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=1429269686.1885.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yeohchunyeow@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.