public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jouni.malinen@atheros.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211/cfg80211: Add vif configuration options
Date: Tue, 19 Aug 2008 15:54:45 +0200	[thread overview]
Message-ID: <1219154085.3476.4.camel@johannes.berg> (raw)
In-Reply-To: <20080818191036.GC4809@jm.kir.nu>

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]

On Mon, 2008-08-18 at 22:10 +0300, Jouni Malinen wrote:

> + * @drop_unencrypted: Whether to drop unencrypted frames
> + *	(0 = no, 1 = yes, -1 = do not change)

Should that be part of some encryption settings instead? Not really
sure.

> + * @userspace_mlme: Whether to use userspace MLME
> + *	(0 = no, 1 = yes, -1 = do not change)

I don't really like this much, it feels like a specific hack to get
wpa_supplicant and mac80211 play together, rather than an API to do this
generically.

What I've been thinking and talking about for quite a long time is to
make cfg80211 more agnostic as to where the MLME lives, and let nl80211
still be able to configure the interface when a userspace MLME is
active. That way, all tools could continue to work regardless of where
the MLME is.

That would, of course, require to finally put wext into cfg80211, make
the wext code capable of sending nl80211 messages to the userspace MLME
and also have nl80211 divert messages to the MLME back to the userspace
MLME unless they are coming from the userspace MLME.

Ultimately, that would allow the userspace MLME to have much more
control while users are still able to use the regular tools for many
things.

Unless, of course, those guys really put d-bus into the kernel and we
can just have the MLME service for a specific interface bound
anywhere...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-08-19 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 19:10 [PATCH] mac80211/cfg80211: Add vif configuration options Jouni Malinen
2008-08-19 13:54 ` 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=1219154085.3476.4.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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