From: Antonio Quartulli <quartulli@atsystem.org>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problems with iwl3945, hard to connect to encrypted networks
Date: Mon, 03 Mar 2008 16:46:28 +0100 [thread overview]
Message-ID: <47CC1D54.7030302@atsystem.org> (raw)
In-Reply-To: <47CC1926.1090708@aitel.hist.no>
try using the iwlwifi module in the compat-wireless-2.6
It seems to work very well here.
In past, I got same problem with kernel module.
Helge Hafting ha scritto:
> I have a Dell830 that uses the 3945 driver.
> I have tried kernels 2.6.23, 2.6.24 and 2.6.35-rc3.
>
> Unencrypted networks seems to work well,
> I usually connect on first try.
>
> Encrypted networks are harder. They work fine
> once I get connected, but I have to try
> very many times before the connection works.
>
> I bring up the interface using
> ifconfig wlan0 up
> and configure it with
> iwconfig wlan0 essid SSID key s:password
>
> If I run iwconfig first, I usually get something
> like this in the dmesg log:
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> If I run iwconfig after ifconfig, I get:
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 00:14:1b:5a:13:40
> wlan0: privacy configuration mismatch and mixed-cell disabled -
> disassociate
> wlan0: RX authentication from 00:14:1b:5a:13:40 (alg=0 transaction=2
> status=0)
> wlan0: authenticated
> wlan0: associate with AP 00:14:1b:5a:13:40
> wlan0: mismatch in privacy configuration and mixed-cell disabled - abort
> association
> wlan0: RX deauthenticaion from 00:14:1b:5a:13:40 (reason=2)
> wlan0: deauthenticated
>
>
> Try fifty times - and sometimes it just works. Most of the time I get
> this exact failure. The same happens with other access points that uses
> encryption. Retrying manually is tedious though.
>
> I compiled the kernels myself using gcc-4.2.3 from debian.
> The kernel is 64-bit and SMP, to take full advantage of
> the core2duo processor.
>
>
> Helge Hafting
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Antonio Quartulli,
Student of Computer Science at University of Pisa
Web: www.quartulli.org
next prev parent reply other threads:[~2008-03-03 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 15:28 Problems with iwl3945, hard to connect to encrypted networks Helge Hafting
2008-03-03 15:46 ` Antonio Quartulli [this message]
2008-03-04 9:11 ` Helge Hafting
2008-03-04 10:20 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 12:03 Helge Hafting
2008-03-05 12:22 ` 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=47CC1D54.7030302@atsystem.org \
--to=quartulli@atsystem.org \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-wireless@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).