From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: remove shared key todo
Date: Mon, 16 Jun 2008 22:46:16 +0200 [thread overview]
Message-ID: <1213649176.3803.55.camel@johannes.berg> (raw)
In-Reply-To: <1213648729.18384.11.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
> > 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.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-06-16 20:47 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 [this message]
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
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=1213649176.3803.55.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.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;
as well as URLs for NNTP newsgroup(s).