From: Naveen Singh <sningh@atheros.com>
To: <gregkh@suse.de>
Cc: <devel@linuxdriverproject.org>, <linux-wireless@vger.kernel.org>,
Naveen Singh <nsingh@atheros.com>
Subject:
Date: Sat, 30 Apr 2011 19:30:38 -0700 [thread overview]
Message-ID: <1304217038-1654-1-git-send-email-sningh@atheros.com> (raw)
From: Naveen Singh <nsingh@atheros.com>
The WPA-PSK association was not going through with 2.6.38
kernel. It was found that supplicant was not able to set
the PTK key. On further analysis it was found that the function
nl80211_set_key in file net/wireless/nl80211.c is returning with
code as -EOPNOTSUPP. This function has been modified to check for
the flag "WIPHY_FLAG_SUPPORTS_SEPARATE_DEFAULT_KEYS"in wiphy
struct. If this flag is not set in the driver init, it returns
from here thereby causing the association to fail. The solution
is to set this flag in driver init as there would be separate
default keys for unicast and multicast packets.
Signed-off-by: Naveen Singh <nsingh@atheros.com>
---
drivers/staging/ath6kl/os/linux/cfg80211.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/ath6kl/os/linux/cfg80211.c b/drivers/staging/ath6kl/os/linux/cfg80211.c
index e87d3aa..ec22408 100644
--- a/drivers/staging/ath6kl/os/linux/cfg80211.c
+++ b/drivers/staging/ath6kl/os/linux/cfg80211.c
@@ -1455,6 +1455,11 @@ ar6k_cfg80211_init(struct device *dev)
wdev->wiphy->cipher_suites = cipher_suites;
wdev->wiphy->n_cipher_suites = ARRAY_SIZE(cipher_suites);
+ /*Support the seprate keys for unicast and multicast packets
+ *This flag is needed because because nl80211 checks for this
+ *flag before calling cfg ops for setting the key.*/
+ wdev->wiphy->flags |= WIPHY_FLAG_SUPPORTS_SEPARATE_DEFAULT_KEYS;
+
ret = wiphy_register(wdev->wiphy);
if(ret < 0) {
AR_DEBUG_PRINTF(ATH_DEBUG_ERR,
--
1.7.0.4
next reply other threads:[~2011-05-01 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 2:30 Naveen Singh [this message]
2011-05-01 9:29 ` Johannes Berg
2011-05-03 1:28 ` set key and separate default keys Jouni Malinen
2011-05-03 17:11 ` Jouni Malinen
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=1304217038-1654-1-git-send-email-sningh@atheros.com \
--to=sningh@atheros.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=nsingh@atheros.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.