From: Dan Williams <dcbw@redhat.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: dragoran <drago01@gmail.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] iwl3945/mac80211 cannot connect to dynamic wep network
Date: Tue, 23 Oct 2007 10:07:33 -0400 [thread overview]
Message-ID: <1193148453.8648.20.camel@localhost.localdomain> (raw)
In-Reply-To: <1193127280.3069.261.camel@debian.sh.intel.com>
On Tue, 2007-10-23 at 16:14 +0800, Zhu Yi wrote:
> On Tue, 2007-10-23 at 09:54 +0200, dragoran wrote:
> > I really have bo idea what this means... with ipw3945 (ieee80211
> > based) the same network works just fine.
>
> This is related to mac80211, not the driver. That's why ipw3945 works.
> Does this patch work for you?
>
> http://marc.info/?l=linux-wireless&m=118715117523167&w=2
Was there ever a conclusion to this patch? ISTR it went through a
couple comments and was more or less rejected as the wrong approach.
Can anyone comment as to what the _right_ approach is? Not being able
to connect to dynamic WEP networks is not acceptable, what needs to be
done to make this work?
Thanks,
Dan
next prev parent reply other threads:[~2007-10-23 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 7:54 iwl3945/mac80211 cannot connect to dynamic wep network dragoran
2007-10-23 8:14 ` [ipw3945-devel] " Zhu Yi
2007-10-23 8:56 ` dragoran
2007-10-23 14:07 ` Dan Williams [this message]
2007-10-23 17:37 ` Johannes Berg
2007-10-24 15:07 ` Dan Williams
2007-10-25 13:29 ` Johannes Berg
2007-10-25 13:49 ` Dan Williams
2007-10-25 13:57 ` Johannes Berg
2007-10-28 5:18 ` Dan Williams
2007-10-28 10:28 ` Johannes Berg
2007-10-28 17:36 ` Jouni Malinen
2007-10-28 17:54 ` Johannes Berg
2007-10-28 18:49 ` Jouni Malinen
2007-10-29 14:42 ` Johannes Berg
2007-10-26 10:32 ` [PATCH] " dragoran
2007-10-26 10:43 ` Johannes Berg
2007-10-26 10:53 ` dragoran
2007-10-26 10:43 ` [PATCH] fix dynamic wep dragoran
2007-10-26 10:55 ` Johannes Berg
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=1193148453.8648.20.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=drago01@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.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