[ipw3945] MASTER - on open network - fails to connect

It appears the problem was what you thought it might be... that wireless-tools is too old and out of date for the kernel api.

I tried wireless-* foo in /etc/network/interfaces and that worked fine. I also tried using wpa-driver ipw and that was enough to make it work. But when using ipw driver it gave me some ioctl errors since it wasn't the proper driver to use. If I didn't specify the driver (it uses wext) or specified wext it would never obtain an ip address.

Chris

Tried the older wpasupplicant version you uploaded

http://people.ubuntu.com/~asac/wpasupplicant_0.5.8-0ubuntu1_amd64.deb

but it didn't seem to help either.

Alexander, was it you who discussed this with Chris? Can you please take a look?

Chris, can you please test if setting essid manually (using iwconfig) to "" (nothing) helps if you do that right before connecting through network-manager? (Remember: this bug is about open network)

I tested again tonight with the Gutsy Tribe-4 i386 live cd and the results appeared to be the following:

ifup with wpasupplicant works most of the time, I managed to get it to fail sometimes but not very often. Its usable but can be irritating, when it decides to fail it usually does it repeatedly.

Network Manager most of the time only sees the open AP and can not connect to it. For some reason it could not see the WPA AP most of the time. I also noticed that several times (at least) when the system first booted it actually would already be connected to the open AP by the time it finished booting and I ran ifconfig. However NM did not show the network as connected. I don't know if that was related to why I was not seeing the WPA AP, perhaps it didn't see it since it was already connected to the open AP when it did the scan? Also if I tried to connect to the open AP after it had already connected on boot via NM it would not connect to the network. Somehow at one point (I don't remember the details) I was able to get NM to connect (associate) to the open AP but it did not run dhclient to get an ip address. I was able at that point to run ifup and it obtained the ip address, I did not have to change anything in /etc/network/interfaces for that to work apparently because it was already associated at that point and it seemed to just run dhclient.

It is possible some of these issues are related to ipw3945 in particular but the fact that ifup/wpasupplicant works the majority of the time makes me think it is just NM being extremely buggy.

probably a kernel issue ... serious review should be done for tribe-6 as ipw3945 is one of the important chipsets (including dell).

Hi Chris,

ok, what i see is that network manager uses wpa_supplicant to setup network, but never receives any association event back.

1. Please stop network-manager completely: /etc/dbu*/even*/25Net* stop ... ensure that you have no wlan/eth1 interface up with ifconfig.

2. Then try supplicant manually:

    1st terminal:
       sudo wpa_supplicant -dd -g /var/run/wpa-supplicant-global 2>&1 | tee /tmp/wpa_supplicant.log

    2nd terminal:
      sudo wpa_cli -g/var/run/wpa-supplicant-global interface_add eth1 "" "" /var/run/wpa_supplicant
      sudo wpa_cli -p/var/run/wpa_supplicant

    (enter interactive shell)
     > AP_SCAN 1
     OK
     > ADD_NETWORK
     0
     > SET_NETWORK 0 ssid "youressid"
     OK
     > SET_NETWORK 0 key_mgmt NONE
     OK
     > ENABLE_NETWORK 0

Now wait a while and post the output of 2nd terminal as well as the wpa_supplicant.log. (don't run dhclient or something ... its of no matter for this test).

Thanks,

 - Alexander

ok i think we nailed down this issue. Chirs, please branch the patched ipw3945 driver sources from https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac, build them and test if connecting to open network succeeds for you.

(Please no statement about other issues ... just, does switching back and forth to open network<->wired work).

Pleas build with kernel headers et al installed, then run:

make IEEE80211_IGNORE_DUPLICATE=y SHELL=/bin/bash

in your source tree ... then copy the kernel module to the right place.

network-manager could do better, but the driver definitly should send associated events in a few more ocassions. Thus, added l-u-m target.

The "can't get a DHCP lease" connection issue with an unencrypted access point seems resolved with the 2007-09-04 ipw3945 driver from http://bazaar.launchpad.net/~asac/intellinuxwireless/ipw3945.asac . Also (still) seems fine connecting using WPA (but that might have always worked due to wpa_supplicant not being quite so fast to make connections).

Gutsy lum d1c010898c4c794c78ffedfe616e9bfd95a49155

ipw3945 module with my fix was released to gutsy. ipw3945 version (modinfo) is 1.2.2mp.ubuntu1.

If you still cannot connect to open networks, reopen.

was fixed in driver ... not a network-manager bug.

Reopening Hardy task. Since we do not have an updated l-u-m in Hardy it can't possibly be fixed already.

Accepted into gutsy-proposed, please test and give feedback here.

 linux-ubuntu-modules-2.6.22 (2.6.22-14.38) gutsy-proposed; urgency=low
 .
   [Amit Kucheria]
 .
   * Poulsbo: Update DRM driver to sync with moblin tree
 .
   [Phillip Lougher]
 .
   * Backport lookup_one_len_nd NFS changes from Unionfs 2.0
     - LP: #137765, 103044
   * Backport unionfs_statfs from Unionfs 2.0
     - LP: #137765, 103044
 .
   [Tim Gardner]
 .
   * postinst does not run depmod correctly.
     - LP: #134193
   * depmod uses incorrect options in postinst and postrm
     - LP: #134193
   * Add STAC9228 DMIC support.
     - LP: #153963
   * l-u-m ships with OLD cx2341x mpeg encoder firmware
     - LP: #99107
   * Prevent hard system locks when lirc_pvr150 is loaded
     - LP: #156747
   * Fix version ipw3945 string for Centrino Mobile Test (CMT).
     - LP: #128360

l-u-m copied from gutsy-proposed to gutsy-updates.