From: Chr <chunkeey@web.de>
To: Stefan Puch <stefan.puch@mail.uni-oldenburg.de>
Cc: linux-net@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: prism54: WPA/RSN support for fullmac cards
Date: Wed, 25 Apr 2007 15:47:20 +0200 [thread overview]
Message-ID: <200704251547.20248.chunkeey@web.de> (raw)
In-Reply-To: <462E55EA.4030900@mail.uni-oldenburg.de>
On Tuesday, 24. April 2007, Stefan Puch wrote:
> Chr wrote:
> >> I thought that at least chunkeey got a working connection.... obviously not.
> >>
> > Of course it works! But not with every AP... only with "hostapd".
> > (I don't have anything else to try).
>
> Perhaps we can do a meeting after your ABI and do some tests with another AP?
Now, I'm "finish" with the "practical" part... ;-).
But, I won't be here the next few weeks, (field excursion, another field excursion
and did I mention lots of field excursion?) .
>
> > But please, before you waste your time with _some_ fullmac anomalies,
> >
> > get the last wireless-dev.git tree.
> > There is a SOFTMAC driver for all prism54 chips now!
> >
> > You only need a firmware:
> > http://daemonizer.de/prism54/prism54-fw/fw-softmac/lmac_2.7.0.0.arm
> > (rename it to "isl3886" and put it in the right place).
>
> - I got the wireless-dev.git tree version g5363171f.
> - I could successfully use the SOFTMAC driver with my Netgear WG511 and the
> Fritz!Box Fon WLAN 7170
> - WPA and WPA2 encryption worked fine (very good work Thanks!)
> - only the "Act" (yellow) LED on the WLAN-Adapter was flashing very very fast
> the whole time, I hope it doesn't give up to fast (perhaps someone could set
> the rate a little bit down?)
>
Na, don't worry, I've copied more than 4 GB over the WIFI link, it should be stable.
But, I know that some cheap APs may have "stability" problems, I ditched my old
Netgear WG624 for that reason.
> - if I can do some further testings that may help you let me know
>
(Do you know why your AP rejects the FULLMAC driver?
If you have another card you can "monitor" for "deauth" or
"disassoc" mlmes, they include a "reason" code)
Thanks,
Chr.
next prev parent reply other threads:[~2007-04-25 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <462336B1.4090006@mail.uni-oldenburg.de>
2007-04-16 13:55 ` prism54: WPA/RSN support for fullmac cards John W. Linville
2007-04-16 14:09 ` Dan Williams
2007-04-17 18:33 ` Stefan Puch
2007-04-17 19:12 ` Michael Wu
2007-04-17 20:24 ` Luis R. Rodriguez
2007-04-24 18:49 ` Stefan Puch
2007-04-24 18:48 ` Michael Wu
2007-04-24 19:07 ` Stefan Puch
2007-04-17 19:23 ` Chr
2007-04-18 9:00 ` Stefan Puch
2007-04-18 9:49 ` Chr
2007-04-24 19:09 ` Stefan Puch
2007-04-25 13:47 ` Chr [this message]
[not found] ` <200704261228.01889.chunkeey@web.de>
[not found] ` <46320D71.60409@mail.uni-oldenburg.de>
2007-04-27 16:21 ` Chr
2007-04-28 15:31 ` Stefan Puch
2007-04-28 18:02 ` Stefan Puch
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=200704251547.20248.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=linux-net@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stefan.puch@mail.uni-oldenburg.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).