From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>, Thomas Pedersen <thomas@cozybit.com>
Subject: [RFC 2/3] cfg80211: disallow setting channel on WDS interfaces
Date: Fri, 11 May 2012 20:08:19 +0200 [thread overview]
Message-ID: <20120511181044.938534049@sipsolutions.net> (raw)
In-Reply-To: 20120511180817.974687689@sipsolutions.net
From: Johannes Berg <johannes.berg@intel.com>
If it worked (Felix says it doesn't right now), the
typical use-case for WDS interfaces would be to be
slaved to AP mode interfaces. Therefore, it isn't
necessary to set the channel on WDS interfaces. As
they don't support powersave or anything like that,
they also couldn't use a different channel anyway.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
net/wireless/nl80211.c | 6 ++----
net/wireless/wext-compat.c | 1 -
2 files changed, 2 insertions(+), 5 deletions(-)
--- a/net/wireless/nl80211.c 2012-05-11 19:34:13.000000000 +0200
+++ b/net/wireless/nl80211.c 2012-05-11 20:01:08.000000000 +0200
@@ -1128,9 +1128,8 @@ static int parse_txq_params(struct nlatt
static bool nl80211_can_set_dev_channel(struct wireless_dev *wdev)
{
/*
- * You can only set the channel explicitly for WDS interfaces,
- * all others have their channel managed via their respective
- * "establish a connection" command (connect, join, ...)
+ * You can't set the channel explicitly, it is managed with
+ * the "establish a connection" commands (connect, join, ...)
*
* For AP/GO and mesh mode, the channel can be set with the
* channel userspace API, but is only stored and passed to the
@@ -1144,7 +1143,6 @@ static bool nl80211_can_set_dev_channel(
*/
return !wdev ||
wdev->iftype == NL80211_IFTYPE_AP ||
- wdev->iftype == NL80211_IFTYPE_WDS ||
wdev->iftype == NL80211_IFTYPE_MESH_POINT ||
wdev->iftype == NL80211_IFTYPE_MONITOR ||
wdev->iftype == NL80211_IFTYPE_P2P_GO;
--- a/net/wireless/wext-compat.c 2012-05-11 19:45:41.000000000 +0200
+++ b/net/wireless/wext-compat.c 2012-05-11 20:01:08.000000000 +0200
@@ -796,7 +796,6 @@ static int cfg80211_wext_siwfreq(struct
case NL80211_IFTYPE_ADHOC:
return cfg80211_ibss_wext_siwfreq(dev, info, wextfreq, extra);
case NL80211_IFTYPE_MONITOR:
- case NL80211_IFTYPE_WDS:
freq = cfg80211_wext_freq(wdev->wiphy, wextfreq);
if (freq < 0)
return freq;
next prev parent reply other threads:[~2012-05-11 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 18:08 [RFC 0/3] mesh/wds channel changes & clarifications Johannes Berg
2012-05-11 18:08 ` [RFC 1/3] cfg80211: provide channel to join_mesh function Johannes Berg
2012-05-11 19:10 ` Thomas Pedersen
2012-05-11 19:15 ` Johannes Berg
2012-05-11 18:08 ` Johannes Berg [this message]
2012-05-11 18:08 ` [RFC 3/3] cfg80211: clarify set_channel APIs 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=20120511181044.938534049@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@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 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.