From: Sven Eckelmann <sven@narfation.org>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
Antonio Quartulli <ordex@autistici.org>,
Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Ray Gibson <rgibson@futurec.net>
Subject: [RFC 0/3] WPA_NONE support in mac80211/ath9k
Date: Mon, 28 Jan 2013 17:11:02 +0100 [thread overview]
Message-ID: <30210911.93HAZKKtRJ@bentobox> (raw)
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
Hi,
I've tried to use WPA_NONE together with ath9k (other people reported
problems, but said it would be batman-adv related [1]). I ran into three
smaller problems and worked around them. I am not sure what kind of support
mac80211 should have for WPA_NONE, but maybe also someone else is trying
it and could use this as a reference. Nevertheless, IBSS/RSN should be
preferred.
I've used a wpa_supplicant with fixed-ibss support [2,3] on an vif configured
as adhoc device.
ap_scan=2
fast_reauth=1
network={
ssid="ESSID"
mode=1
proto=WPA
frequency=2422
key_mgmt=WPA-NONE
pairwise=NONE
group=CCMP
psk="abcd1234"
bssid=02:00:de:ad:be:fe
}
First problem was related in the way the decryption is done. No unicast frames
could be decrypted because the group key (the only one set for WPA_NONE)
wasn't allowed to be used for unicast decryption.
The second problem was the replay detection. Replay detection doesn't work
with WPA_NONE and therefore has to be disabled.
The third problem was the inability to set the key when no link was
established. This lead to unencrypted broadcast packets sent over the air...
not really nice. Therefore, I've just disabled the check [4] for now.
I was informed by Antonio Quartulli about the controversy to use
!sta->sdata->u.ibss.control_port to check for for non-IBSS/RSN mode. Just
think about it is a placeholder for the imaginary function
"ieee80211_ibss_is_wpanone(...)".
Is the inability to use WPA_NONE with ath9k/mac80211 intended or just a
regression nobody noticed? In the latter case, any things which should
be changed to make the patches upstream ready?
Kind regards,
Sven
[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2013-January/008895.html
[2] http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=commitdiff;h=913e3cf794cccf19d551d936a16c7d91acb5e834
[3] http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=commitdiff;h=9e2af29f9bf065099b9a2abceaf40ac0e1bf86fa
[4] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=fffd0934b9390f34bec45762192b7edd3b12b4b5
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-01-28 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 16:11 Sven Eckelmann [this message]
2013-01-28 16:11 ` [RFC 1/3] mac80211: Allow group key for IBSS WPA_NONE Sven Eckelmann
2013-01-28 16:11 ` [RFC 2/3] mac80211: Ignore CCMP replays " Sven Eckelmann
2013-01-28 16:11 ` [PATCH 3/3] nl80211: Allow to set IBSS key even before IBSS_JOIN Sven Eckelmann
2013-01-29 19:23 ` [RFC 0/3] WPA_NONE support in mac80211/ath9k Johannes Berg
2013-01-29 22:08 ` Sven Eckelmann
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=30210911.93HAZKKtRJ@bentobox \
--to=sven@narfation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ordex@autistici.org \
--cc=rgibson@futurec.net \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
/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).