Network Manager rejects WEP keys for IPW 3945

[andrew petts]

Binary package hint: network-manager

Hello. I am using Ubuntu 7.04 with the said wireless card. I can see the network. When i try to connect it asks for my WEP, which is entered correctly. It then does not connect to the network.

Any fix for this would be greatly appreciated

[Alexander Sack (asac)]

this was fixed by a driver update in gutsy. Please test latest daily livecd to verify that its fixed for you too.

[Alexander Sack (asac)]

latest isos are at http://cdimage.ubuntu.com/daily/current/

[mb (maxbloemer)]

does not work for me. doesn't work with gusty-beta live cd.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137963

[Alexander Sack (asac)]

this was fixed in gutsy.

[Alexander Sack (asac)]

tim or anybody else from the kernel team: the patch i submitted for 3945 should fix this in feisty as well. maybe an SRU?

[Alexander Sack (asac)]

this isn't a network-manager issue

[mb (maxbloemer)]

yep. I think it's a ipw3945 or a ieee802111 bug.

[Janna (horsecrazyinca)]

I'm running Gutsy with the latest updates with an Intel 3945ABG. I can't connect with WEP (or WPA, although I haven't tried that recently). Unencrypted connections work fine. I'll be eagerly awaiting a fix!

[Brian Avery (briansvgs)]

I am having problems with this as well. I can connect to wireless networks protected with wep, and ping works, but when I open firefox, it can not find google or anything else.

[Brian Avery (briansvgs)]

oh, and my card is the ipw3945 as well.

[Colin Marquardt (ubuntu-marquardt-home)]

My girlfriend's laptop with ipw3945 can connect to unprotected networks and WPA2 networks, but not to a WEP network (doesn't even get a connection). These are all different WLAN routers though. Gutsy, updated about a week ago.

[daniel2501 (daniel2501)]

Seems to be fixed in the latest Gutsy updates.

On 10/12/07, Colin Marquardt <email address hidden> wrote:
>
> My girlfriend's laptop with ipw3945 can connect to unprotected networks
> and WPA2 networks, but not to a WEP network (doesn't even get a
> connection). These are all different WLAN routers though. Gutsy, updated
> about a week ago.
>
> --
> Intel pro/wireless 3945ABG WEP can't connect : its happened to me too
> https://bugs.launchpad.net/bugs/139080
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Eric Murphy (murphye)]

I tried the RC1 AMD64 release, and I can finally connect. I have tried to get this working for many months.

For some reason I needed to enter in my password under the HEX value rather than ASCII or passphrase. That is confusing, but it works.

[Brian Avery (briansvgs)]

I tried wicd with the gutsy beta (all updates installed), and that succeeded in connecting to my wep network, but networkmanager still won't work. I will try again once I get gutsy final and see if it works now.

[Steven Harper (stevenharperuk)]

With the latest Live CD i386 (todays proper Gutsy release)

I am seeing the same problem on my Acer Aspire 5630 that has the Intel pro/wireless 3945ABG hardware

When I attempt to connect to a WEP (HEX) network

In /var/log/syslog

I see the authentication process only getting to stage 2

<info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
<info> old device 'eth1' activating, won't change.
<info> Activation (eth1\wireless): association took too long (/120s), failing activation.

This is preventing me from moving to Gutsy, I would love to see a high priority assigned to this bug

Steve

[Steven Harper (stevenharperuk)]

I can confirm that the Intel pro/wireless 3945ABG will connect if there is NO WEP security
with the latest Live CD i386 (proper Gutsy release)

Steve

[Torpiii (torpiii)]

With my dell inspiron 6400 and the Intel 3945 abg wifi card and the final release of Gutsy, i can't connect to my wifi network too (wep security, static ip address). I can see the access point and the strength of the signal, but i'm unable to complete the connection.

[andrew petts (pettsium)]

The way I finally got mine to work is to create a keyring for the passphrase to the wireless network. it does mean typing in a password every time i want to connect to my home network but at least i can connect

[Robbie G (robbie-cartwood-nee-grimwood)]

Issue still present in Hardy Heron 8.04 (with WPA)

I have a Fujitsu Siemens Amilo Pi 1505 with a 3945ABG wireless card which regularly fails to connect to a WPA network though occasionally I note that it does connect. This issue was present under 7.10.

The commonly reported message in syslog is:
error getting ESSID for device eth1: Resource temporarily unavailable

and when it times out the following message is written:
Activation (eth1/wireless): association took too long (>120s), failing activation

For reference, I have another Ubuntu 7.10 Fujitsu Siemens laptop a V2040 with "Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)" also another Ubuntu 7.10 IBM laptop with an Ralink RA2500 PCMCIA card. Both of these machines connect to the network immediately and never drop the connection. The IBM is on 24x7.

The relevant portion of the syslog is attached.

[Robbie G (robbie-cartwood-nee-grimwood)]

Issue still present in Hardy Heron 8.04 (with WPA)

I have a Fujitsu Siemens Amilo Pi 1505 with a 3945ABG wireless card which regularly fails to connect to a WPA network though occasionally I note that it does connect. This issue was present under 7.10.

The commonly reported message in syslog is:
error getting ESSID for device eth1: Resource temporarily unavailable

and when it times out the following message is written:
Activation (eth1/wireless): association took too long (>120s), failing activation

For reference, I have another Ubuntu 7.10 Fujitsu Siemens laptop a V2040 with "Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)" also another Ubuntu 7.10 IBM laptop with an Ralink RA2500 PCMCIA card. Both of these machines connect to the network immediately and never drop the connection. The IBM is on 24x7.

The relevant portion of the syslog is attached.

[Robbie G (robbie-cartwood-nee-grimwood)]

An update to clarify my statement "occasionally I note that it does connect".

After 20 startups I have 6 successful wireless LAN connects and 14 failures. It appears to be totally random.

[tommaso gardumi (tommaso-gardumi)]

i'm running ubuntu 7.10 on a clevo notebook https://wiki.ubuntu.com/LaptopTestingTeam/ClevoM720R
my wireless card intel pro 3945 abg is recognized and working with driver ipw3945.
the problem is that i can connect t my network only when i'm very close to my access point, and the card is not able to find other networks when there are
encrypted security.
also a friend of mine with my same card on an acer aspire running ubuntu 7.10 same kernel is able to see and connect to networks that i can't even see...
is there a way i can solve this by looking at my friend configurations/options whatever?
how can i help myself and other users? i ready for testing

[AleX-75 (alessandro-bonade)]

I run Ubuntu 7.10 on a DELL D830 notebook.

My wireless card INTEL PRO 3945AB is recognized but it doesn't connect to my WLAN.

I tried with WPA, WEP and none authentication but there is no way to get it work.

Sometimes I get the connection but I lose it very quickly.

With another notebook with Windows XP I cab connect without problems.

The sistem log reports the following lines:

"error getting ESSID for device eth1: Resource temporarily unavailable"

and after a while

"Activation (eth1/wireless): association took too long (>120s), failing activation"

This is a big problem for me, please could you help me to solve it?

Best regards.

[Lynne Lawrence (lynnel02)]

Has anyone succeeded in getting this to work?

I have a fully updated Gutsy installation on a brand new Dell Inspiron 1525 with an Intel PRO 3945ABG wireless card. I am able to connect to my Access Point fine if I run the AP open. If I enable WEP on the AP, no connect. I have tried both the network manager app that came with Ubuntu and Wicd - same results. I just get something like this in my syslog:

Apr 24 22:30:14 dell-desktop dhclient:
Apr 24 22:30:15 dell-desktop dhclient: Listening on LPF/eth1/00:1f:3c:28:be:d7
Apr 24 22:30:15 dell-desktop dhclient: Sending on LPF/eth1/00:1f:3c:28:be:d7
Apr 24 22:30:15 dell-desktop dhclient: Sending on Socket/fallback
Apr 24 22:30:16 dell-desktop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
Apr 24 22:30:24 dell-desktop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
Apr 24 22:30:37 dell-desktop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
Apr 24 22:30:45 dell-desktop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
Apr 24 22:30:47 dell-desktop dhclient: No DHCPOFFERS received.

I know that my keys are correct and I am able to make wireless, WEP, connections using an old Thinkpad (also running Ubuntu Gutsy) without any issue. Because my Thinkpad has no problem, and I get the same results whether using wicd or network-manager, I am thinking that this must by a card or driver problem...?

I find this very disappointing, and have no intentions of running an open AP. If I cannot get this resolved, I am afraid I will have to return my nice new Inspiron and search for something that works :-(

Please let me know of any working solutions.

Thanks!

Lynne

[Mackenzie Morgan (maco.m)]

Is this just with Network Manager for you guys? Does it work if you do it from the command line? For example:
sudo iwconfig wlan0 essid linksys key DEADBEEF0123
sudo dhclient wlan0

For me, with my 3945 using ipw3945 or iwl3945 drivers and for my 4965 using the iwl4965 driver, command line works, but Network Manager rejects all WEP keys. Is this the case with you as well? I am using Hardy, but I haven't been able to connect to WEP using NM since Feisty at least.

[Alexander Sack (asac)]

On Tue, Aug 12, 2008 at 03:19:08PM -0000, Mackenzie Morgan wrote:
> Is this just with Network Manager for you guys? Does it work if you do it from the command line? For example:
> sudo iwconfig wlan0 essid linksys key DEADBEEF0123
> sudo dhclient wlan0
>
> For me, with my 3945 using ipw3945 or iwl3945 drivers and for my 4965
> using the iwl4965 driver, command line works, but Network Manager
> rejects all WEP keys. Is this the case with you as well? I am using
> Hardy, but I haven't been able to connect to WEP using NM since Feisty
> at least.
>

WEP is a unmature standard with no real error detection - and no real
security btw. So buggy drivers that eat packets for a while will make
network-manager believe that there was a discoonect, while forcefully
doing things by hand might not.

This is nothing that we can easily change if we dont want to abandon
the main principals of NM's approach.

 - Alexander

[Mackenzie Morgan (maco.m)]

I know it's no real security. Not my network, but try telling my school's CS department that they're a bunch of idiots ;) So it's likely a driver bug then, not a NM bug? OK, that's fun. Perhaps a bug regarding "ipw3945, iwl3945, and iwl4965 eat packets" is needed then?

[Alexander Sack (asac)]

On Tue, Aug 12, 2008 at 05:35:34PM -0000, Mackenzie Morgan wrote:
> I know it's no real security. Not my network, but try telling my
> school's CS department that they're a bunch of idiots ;) So it's likely
> a driver bug then, not a NM bug? OK, that's fun. Perhaps a bug
> regarding "ipw3945, iwl3945, and iwl4965 eat packets" is needed then?
>

if you have a chance to test iwl3945 drivers currently in intrepid,
please do so.

 - Alexander

[Lynne Lawrence (lynnel02)]

> if you have a chance to test iwl3945 drivers currently in intrepid,
> please do so.
>
>
> - Alexander
>
>
I have been able to get my PRO/Wireless 3945ABG wireless card working
with the iwl3945 driver. I am currently using it with the network admin
tool delivered with my version of Ubuntu:

 > cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

Here are my notes on the install:

Installed the iwl3945 driver as described at:

http://linuxwireless.org/en/users/Download

Modified /etc/udev/rules.d/70-persistent-net.rules, commenting out the
eth1 device for the ipw3945 driver:

# PCI device 0x8086:0x4222 (ipw3945)
# Commented out to test iwl3945 driver
# SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1f:3c:28:be:d7",
NAME="eth1"

Added the following to the end of /etc/modprobe.d/blacklist:

blacklist ipw3945
blacklist ieee80211
blacklist ieee80211_crypt

Added the following to the end of /etc/modules:

iwlwifi_mac80211
iwl3945

During my travels in trying to get this to work I did install wicd. I
originally got the card to work with wicd/iwl3945 but found that, as I
moved from site to site, wicd did not reconfigure my passwords and/or
password types correctly (can't remember the details, but I viewed the
config files and they were definitely not being updated properly).
Because of this, I removed wicd and am now using the network-admin tool
that comes with Ubuntu and all is reasonably well. I find that, if I
loose my wireless connection, I sometimes have to reboot to recover it
and sometimes not. Ah well, at least it works generally.

Thanks to all who have worked getting the drivers to work!

Lynne Lawrence

[LumpyCustard (orangelumpycustard)]

Please close for Feisty as Won't Fix? This goes for all the other Feisty bugs.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-backports-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

[Sergio Zanchetta (primes2h)]

Sorry, I meant linux-ubuntu-modules-2.6.22 task.

[Hew (hew)]

Closing EoL SRU tasks.