From: Jiri Benc <jbenc@suse.cz>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Hong Liu <hong.liu@intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>,
linux-wireless@vger.kernel.org
Subject: Re: [patch]mac80211: add support for iwlist channel
Date: Wed, 20 Jun 2007 18:25:58 +0200 [thread overview]
Message-ID: <20070620182558.47871535@griffin.suse.cz> (raw)
In-Reply-To: <4679672D.4060503@linux.intel.com>
On Wed, 20 Jun 2007 10:43:09 -0700, James Ketrenos wrote:
> [...]
> /**
> * enum ieee80211_channel_flags - Channel flag bit values
> * @IEEE80211_CHAN_W_TUNE: Hardware can tune to this channel
> * @IEEE80211_CHAN_W_ACTIVE: Channel can be used for active scanning
> * @IEEE80211_CHAN_W_IBSS: Hardware can act as IBSS Master
> * @IEEE80211_CHAN_W_RADAR: Radar spectrum enforcement applies
> * @IEEE80211_CHAN_W_TX_ALLOWED: Tx is allowed
Looks good, except...
> [...]
> * A channel without the TX_ALLOWED bit set *can not* be used
> * for any type of transmission and can only be used for passive
> * listening. This is useful for performing network audits.
I don't find this useful. The stack isn't aware of anything like this.
Do you plan to add a support for this flag? Also, cfg80211/nl80211
would need to be taught of it.
Thanks,
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-06-20 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 8:47 [patch]mac80211: add support for iwlist channel Hong Liu
2007-06-19 5:12 ` Michael Wu
2007-06-20 3:03 ` Hong Liu
2007-06-20 3:24 ` Larry Finger
2007-06-20 7:08 ` Michael Wu
2007-06-21 1:43 ` Hong Liu
2007-06-19 8:50 ` Jiri Benc
2007-06-20 2:10 ` Hong Liu
2007-06-20 9:55 ` Jiri Benc
2007-06-20 17:43 ` James Ketrenos
2007-06-20 16:25 ` Jiri Benc [this message]
2007-06-20 18:19 ` James Ketrenos
2007-06-20 17:05 ` Jiri Benc
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=20070620182558.47871535@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=jketreno@linux.intel.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