From: Dan Williams <dcbw@redhat.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: remove shared key todo
Date: Tue, 17 Jun 2008 15:02:51 -0400 [thread overview]
Message-ID: <1213729371.30192.26.camel@localhost.localdomain> (raw)
In-Reply-To: <1ba2fa240806171141sda9c0eak747adbba3a6fe4db@mail.gmail.com>
On Tue, 2008-06-17 at 21:41 +0300, Tomas Winkler wrote:
> On Tue, Jun 17, 2008 at 9:12 PM, Dan Williams <dcbw@redhat.com> wrote:
> > On Mon, 2008-06-16 at 22:46 +0200, Johannes Berg wrote:
> >> > > I have no idea. Usually, you don't even do open auth for IBSS, there's
> >> > > just no point. Unless you get into IBSS with encryption, but we don't
> >> > > really support that yet, and we probably never will actually support
> >> > > that without the userspace MLME in wpa supplicant.
> >> >
> >> > IBSS + WEP works at least for ipw2200 and other non-mac80211 cards; I
> >> > can check it out with mac80211 if you like.
> >>
> >> Yeah, no, +WEP should work. I haven't specifically tested it but I see
> >> no reason for it not to work.
> >>
> >> > Any particular reason IBSS would require a userspace MLME? There
> >> > shouldn't be any rekeying of any kind with adhoc, since there's no
> >> > central station to coordinate the rekying. AFAIK with IBSS you just use
> >> > the given PSK at creation time, and never change it. That shouldn't be
> >> > too hard to handle, right?
> >>
> >> Well, I was really thinking of RSN/WPA, and last I checked
> >> wpa_supplicant didn't even support that with IBSS, and I think it
> >> requires userspace MLME because you have to do the auth/assoc sequence
> >> with each peer etc.
> >
> > wpa_supplicant _should_ support WPA-PSK with IBSS, you set
> > proto=WPA-NONE to do this and I assume it just sends the PSK to the
> > driver and never changes it. I haven't tested it a long time though.
> >
> > Dan
> >
> #~ cat wpa_supplicant.conf
> # mode: IEEE 802.11 operation mode
> # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
> # 1 = IBSS (ad-hoc, peer-to-peer)
> # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
> # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
> # to be set to 2 for IBSS. WPA-None requires following network block options:
> # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
> # both), and psk must also be set.
Yeah, key_mgmt=WPA-NONE, thanks for the correction. Any idea if this
works already on iwlwifi?
Dan
prev parent reply other threads:[~2008-06-17 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 18:55 [PATCH] mac80211: remove shared key todo Johannes Berg
2008-06-16 20:19 ` Dan Williams
2008-06-16 20:21 ` Johannes Berg
2008-06-16 20:25 ` Johannes Berg
2008-06-16 20:38 ` Dan Williams
2008-06-16 20:46 ` Johannes Berg
2008-06-16 21:47 ` Tomas Winkler
2008-06-17 18:12 ` Dan Williams
2008-06-17 18:41 ` Tomas Winkler
2008-06-17 19:02 ` Dan Williams [this message]
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=1213729371.30192.26.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.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).