From: dragoran <drago01@gmail.com>
To: dragoran dragoran <drago01@gmail.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
Dan Williams <dcbw@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
John Linville <linville@redhat.com>, Jiri Benc <jbenc@suse.cz>,
ipw3945-devel@lists.sourceforge.net, jketreno@linux.intel.com
Subject: Re: mac80211 does not support WPA when used with wext
Date: Tue, 10 Apr 2007 09:13:52 +0200 [thread overview]
Message-ID: <461B3930.6040203@gmail.com> (raw)
In-Reply-To: <f6ca9fed0704081527j641a4ecat44151e107cab7342@mail.gmail.com>
ok I tested it again with linvilles f7 test kernel (wireless-git + your
patches + iwlwifi).
again nm detect the card as wpa and it finds the wpa enabled network.
But it fails to connect (does not even ask for a key). So I tryed to use
wpa_supplicant by hand ( with a config that works fine with ipw3945 ;
ieee80211) . Its seems not to be related to iwlwifi but to a ioctl that
mac80211 does not support (when used with wext).
----
Own MAC address: 00:18:de:05:f7:9e
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
----
notice the *ioctl[SIOCSIWAUTH]: Operation not supported* what is
SIOCSIWAUTH and how does it not being supproted affect wpa/wext support?
next prev parent reply other threads:[~2007-04-10 7:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 9:36 mac80211 does not support WPA when used with wext dragoran
2007-03-31 10:00 ` Johannes Berg
2007-03-31 10:11 ` dragoran
2007-03-31 11:19 ` dragoran
2007-03-31 16:37 ` Michael Buesch
2007-03-31 16:39 ` Michael Buesch
2007-03-31 17:57 ` Dan Williams
2007-03-31 17:48 ` Dan Williams
2007-03-31 17:59 ` Jouni Malinen
2007-03-31 18:09 ` Larry Finger
2007-03-31 19:03 ` Michael Wu
[not found] ` <f6ca9fed0703311256m1b14ec35p836a62de532dd804@mail.gmail.com>
2007-03-31 21:00 ` Michael Wu
2007-04-01 0:50 ` Dan Williams
2007-04-02 3:50 ` WPA does not connect to bcm43xx-mac80211 when using NetworkManager Larry Finger
2007-04-02 4:12 ` Dan Williams
2007-04-03 14:26 ` Larry Finger
2007-04-02 5:26 ` Michael Wu
2007-04-01 8:18 ` mac80211 does not support WPA when used with wext Johannes Berg
[not found] ` <f6ca9fed0704081445u5536e596m4ca4caeb44f7f87@mail.gmail.com>
2007-04-08 21:54 ` Michael Wu
[not found] ` <f6ca9fed0704081527j641a4ecat44151e107cab7342@mail.gmail.com>
2007-04-10 7:13 ` dragoran [this message]
2007-04-10 12:25 ` Dan Williams
2007-04-10 14:34 ` dragoran dragoran
2007-04-10 14:39 ` Larry Finger
2007-04-10 14:44 ` dragoran dragoran
2007-04-01 0:55 ` Dan Williams
2007-04-01 1:21 ` Michael Wu
2007-04-01 4:51 ` 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=461B3930.6040203@gmail.com \
--to=drago01@gmail.com \
--cc=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@redhat.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).