linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: drago01 <drago01@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Dan Williams <dcbw@redhat.com>, Jouni Malinen <j@w1.fi>,
	ipw3945-devel <ipw3945-devel@lists.sourceforge.net>,
	Zhu Yi <yi.zhu@intel.com>
Subject: Re: mac80211 / iwl3945 + dynamic wep (again)
Date: Sun, 25 Nov 2007 12:00:49 +0100	[thread overview]
Message-ID: <474955E1.30603@gmail.com> (raw)
In-Reply-To: <1195987773.4149.214.camel@johannes.berg>

Johannes Berg wrote:
> Hi,
>
>   
>> First  sorry for the late report, the patches from the old thread fixed 
>> the privacy mismatch issue and now I can connect to a dynamic wep 
>> network. But the connection is not very stable because I get tons of wep 
>> decrypt errors in dmesg (while the connection is working but slow).
>> The same network works fine with ipw3945. Also iwl3945 works fine with 
>> static wep. I tryed the hwcrypt engine (hwcrypt=1) but it did not change 
>> anything.
>> While connectiong with wpa_supplicant I saw that mac80211 does not 
>> support the IW_AUTH_DROP_UNENCRYPTED ioctl while ipw3945 (ieee80211 
>> based) does.
>> Could this be related? ie. mac80211 tryes to decrypt unencrypted frames 
>> instead of dropping them?
>>     
>
> Odd. I'll have to take a look. I recently noticed that mac80211 would
> always *accept* unencrypted frames but it shouldn't try to decrypt them.
>
>   
ok thx, let me now if you need more info / tests.
>> Second problem is that ssid is hidden. I was able to connect to it using 
>> iwl3945 (even with hw_scan) but only with ap_scan=1 (while ap_scan=2 
>> should be used for hidden ssid and thats what nm uses). Non mac80211 
>> based drivers do not work with ap_scan=1 but with ap_scan=2. So this 
>> needs to be fixed somehow so that nm can support both wireless stacks.
>>     
>
> Uh so say that again what works where and what doesn't?
>
>   
sorry for being confusing.
what works:
connect to a hidden ssid with ap_scan=1 in wpa_supplicant.conf
what does not work:
connect to a hidden ssid with ap_scan=2 in wpa_supplicant.conf
---
for non mac80211 drivers its the opposite ie.  ap_scan=2 can connect to 
hidden ssid while ap_scan=1 works
(thats also whats documented in the wpa_supplicant docs and what nm uses).

so NM can't support mac80211 and non mac80211 drivers at the same time 
without ugly hacks due to this issue.

  reply	other threads:[~2007-11-25 11:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 10:02 mac80211 / iwl3945 + dynamic wep (again) drago01
2007-11-25 10:49 ` Johannes Berg
2007-11-25 11:00   ` drago01 [this message]
2007-11-26 12:14     ` Johannes Berg
2007-11-26 16:04       ` Dan Williams
2007-11-26 16:14         ` Johannes Berg
2007-11-26 16:50           ` drago01
2007-11-27  3:49         ` Jouni Malinen
2007-11-27 17:38           ` Dan Williams
2007-11-27  3:40       ` Jouni Malinen
2007-11-26 14:50     ` dragoran
2007-11-26 15:52       ` Johannes Berg
2007-11-26 16:51         ` drago01
2007-11-26 17:01           ` Johannes Berg
2007-11-27  3:34       ` Jouni Malinen
2007-11-28 14:06         ` drago01
2007-11-28 16:50           ` Johannes Berg
2007-11-28 19:45             ` dragoran
2007-11-28 19:47               ` Johannes Berg
2007-11-28 19:50                 ` dragoran
     [not found]             ` <f6ca9fed0801110052ja95e86s9f1842846f0dd8fc@mail.gmail.com>
     [not found]               ` <1200068256.3861.172.camel@johannes.berg>
     [not found]                 ` <f6ca9fed0801160208x40acfb91p8446298fda9e7726@mail.gmail.com>
2008-01-16 18:38                   ` Johannes Berg
2008-01-17 15:38                     ` drago01
2008-01-17 15:40                       ` Johannes Berg
2007-12-03 10:14         ` Johannes Berg
2007-12-03 11:47           ` dragoran
2007-12-04  6:57             ` dragoran
2007-12-04  7:57               ` dragoran
2007-11-26 15:19     ` Dan Williams
2007-11-26 15:47       ` 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=474955E1.30603@gmail.com \
    --to=drago01@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.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;
as well as URLs for NNTP newsgroup(s).