From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org, Luis Carlos Cobo <luisca@cozybit.com>
Subject: Re: [RFC] mac80211/cfg80211: Add BSS configuration options for AP mode
Date: Thu, 07 Aug 2008 16:46:28 +0200 [thread overview]
Message-ID: <1218120388.23048.189.camel@johannes.berg> (raw)
In-Reply-To: <20080807142732.GC5138@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Thu, 2008-08-07 at 17:27 +0300, Jouni Malinen wrote:
> > Yeah, that was a sticky point... But if you want per-BSS information you
> > really have to because right now it's per-hw.
>
> Well, I don't actually need it per-BSS for hardware that I'm most likely
> to work with ;-), but yeah, this is a per-BSS parameter, so in that
> sense your patch is doing the correct thing.
Yeah, ok, I guess I don't really care, do whichever way you want. It'd
be a bit strange to set it with cfg80211 per BSS and have it show up on
different BSSes, but that's about it, and a little strangeness hasn't
hurt anyone ;)
> > Ok, they can't be per VLAN then, true, but then I think we should limit
> > it to _AP just so nobody tries setting them without effect on other
> > devices or overrides, for _STA, what the AP said. For mesh I don't know
> > (adding Luis) and for IBSS I'm not sure either. I suspect you could use
> > it for IBSS too?
>
> I think I'll just make it _AP only for now and if someone ever really
> needs it for something else, they can enable it later.. It is possible
> that new attributes that would be more reasonable for other modes will
> be added in the future for _SET_BSS.
Sure, sounds fine.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-08-07 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 13:40 [RFC] mac80211/cfg80211: Add BSS configuration options for AP mode Jouni Malinen
2008-08-07 13:48 ` Johannes Berg
2008-08-07 14:15 ` Jouni Malinen
2008-08-07 14:18 ` Johannes Berg
2008-08-07 14:27 ` Jouni Malinen
2008-08-07 14:46 ` Johannes Berg [this message]
2008-08-07 16:32 ` Jouni Malinen
2008-08-07 14:25 ` Johannes Berg
2008-08-07 14:32 ` Jouni Malinen
2008-08-07 14:45 ` 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=1218120388.23048.189.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@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