From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Wu <flamingice@sourmilk.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Jiri Benc <jbenc@suse.cz>, Jiri Slaby <jirislaby@gmail.com>
Subject: Re: port of my recent patches to net-2.6.24
Date: Mon, 3 Sep 2007 17:20:02 -0700 [thread overview]
Message-ID: <20070904002002.GU1835@jm.kir.nu> (raw)
In-Reply-To: <1188211612.6756.8.camel@johannes.berg>
On Mon, Aug 27, 2007 at 12:46:52PM +0200, Johannes Berg wrote:
> On Mon, 2007-08-27 at 00:29 -0400, Michael Wu wrote:
> > Patch 12:
> > - int allow_broadcast_always; /* whether to allow TX of broadcast frames
> > - * even when there are no associated STAs
> > - */
> > -
> > Hmm.. that seems useful.. yet nothing is using it? What happen here?
>
> It's "used" in wireless-dev in ioctls, but talking to Jouni he seemed to
> have a better idea instead so was OK with removing it.
For the original reason for adding this (making it easier to do some
continuous TX tests), yes, it can be done in other ways. The only thing
I can think of here would be some special frames (like broadcast data
frames as a beacon of some upper layer service) that would be used by
clients that are capable of receiving frames when not associated (e.g.,
they use monitor mode). This is getting a bit speculative here, so
unless someone can point out a real example that depends on this, I
would go ahead and remove it now.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-09-04 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 7:37 port of my recent patches to net-2.6.24 Johannes Berg
2007-08-26 15:22 ` Ulrich Kunitz
2007-08-27 12:08 ` Johannes Berg
2007-08-27 4:29 ` Michael Wu
2007-08-27 10:46 ` Johannes Berg
2007-09-04 0:20 ` Jouni Malinen [this message]
2007-09-04 13:43 ` Johannes Berg
2007-08-27 13:43 ` Johannes Berg
2007-08-27 13:50 ` Johannes Berg
2007-08-27 23:45 ` Michael Wu
2007-08-28 8:40 ` Johannes Berg
2007-08-28 9:19 ` 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=20070904002002.GU1835@jm.kir.nu \
--to=j@w1.fi \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).