From: chunkeey@web.de
To: Dan Williams <dcbw@redhat.com>
Cc: netdev@vger.kernel.org, chunkeey@web.de
Subject: Re: [PATCH] prism54: wpa support for fullmac cards
Date: Wed, 4 Oct 2006 16:12:26 +0200 [thread overview]
Message-ID: <200610041612.26824.chunkeey@web.de> (raw)
In-Reply-To: <1159962011.2708.19.camel@localhost.localdomain>
On Wed, 4 Oct 2006 13:40 +0200 dcbw@redhat.com wrote:
> On Wed, 2006-10-04 at 12:38 +0200, Jiri Benc wrote:
> > On Tue, 3 Oct 2006 14:57:33 +0200, chunkeey@web.de wrote:
> > > This patch (prism54-en-wpa3.patch) brings WPA/WPA2(RSN) with
> > > TKIP-Cipher to everyone with a FULLMAC Prism GT/Indigo/Duette card.
> > > I removed all the parts(e.g.: Hostapd Support) which are not relevant
> > > for wpa_supplicant (client/managed mode).
> >
> > Are you proposing a patch that removes AP support from the driver or did
> > I understand it wrong?
>
> I believe it adds the support back in, just using standard WE ioctls
> like ENCODEEXT and AUTH rather than the custom HostAP ones... which
> brings up the question whether the hostapd driver for wext (is there
> such a thing?) works well enough.
>
> Dan
>
the AP code never worked. And the hostapd-ioctl interface was designed
for prism2/2.5/3 cards, but not for "fullmac" prism54.
Because the "fullmac" prism54 card does everything(mac-, key- and
station-management) in the firmware and the hostapd_param struct
does neither support the necessary mlme requests/responses (Authentication &
Association frames) nor a param to handle the EAP filter for the stations.
(I wrote a "patch" HostAPD support, but with it's own
firmwareap_param struct and some other hacky things, but it works well.
I can post a diff too, but "be" warned! ;) )
(BTW, hostapd's backend for prism54 uses a "proprietary" interface -
PIMFOR -, which never made it into the kernel.)
Chr.
next prev parent reply other threads:[~2006-10-04 14:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 12:57 [PATCH] prism54: wpa support for fullmac cards chunkeey
2006-10-04 10:38 ` Jiri Benc
2006-10-04 11:40 ` Dan Williams
2006-10-04 14:12 ` chunkeey [this message]
2006-10-04 21:43 ` Jouni Malinen
2006-10-05 17:17 ` chunkeey
2006-10-17 21:32 ` John W. Linville
2006-10-29 12:35 ` [PATCH wireless-2.6-git] prism54: WPA/RSN " chunkeey
2006-10-30 8:50 ` Johannes Berg
2006-10-30 20:17 ` Luis R. Rodriguez
2006-10-31 16:05 ` Dan Williams
2006-10-31 17:53 ` chunkeey
2006-11-03 14:49 ` Dan Williams
2006-11-03 16:06 ` Luis R. Rodriguez
2006-11-03 18:12 ` chunkeey
2006-11-03 18:41 ` Luis R. Rodriguez
2006-11-08 0:39 ` John W. Linville
2006-11-09 17:38 ` chunkeey
2006-11-09 23:16 ` Luis R. Rodriguez
2006-11-09 23:16 ` Luis R. Rodriguez
2006-11-10 14:42 ` Dan Williams
2006-11-17 5:42 ` Dmitry Torokhov
2006-11-17 19:43 ` chunkeey
2006-11-17 20:16 ` Dmitry Torokhov
2006-11-17 20:53 ` chunkeey
2006-11-17 21:02 ` Dmitry Torokhov
2006-11-17 21:09 ` Dmitry Torokhov
2006-11-17 21:35 ` chunkeey
2006-11-18 4:27 ` Dmitry Torokhov
2006-11-18 10:18 ` chunkeey
2006-11-22 7:01 ` Dmitry Torokhov
2006-11-24 15:55 ` chunkeey
[not found] ` <200611250039.03597.dtor@insightbb.com>
2006-11-25 16:50 ` chunkeey
2006-11-26 5:27 ` Dmitry Torokhov
2006-11-26 10:47 ` chunkeey
2006-12-06 1:44 ` John W. Linville
2006-12-06 12:05 ` chunkeey
2006-12-06 14:11 ` Dmitry Torokhov
2006-10-30 20:33 ` 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=200610041612.26824.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=dcbw@redhat.com \
--cc=netdev@vger.kernel.org \
/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).