Description of problem: Can't connect to wireless network using WPA encryption. Version-Release number of selected component (if applicable): NetworkManager-0.6.4-8.el5 How reproducible: Wireless AP: D-Link WBR-1310 ESSID: homelinux WPA TKIP PSK: <passphrase> Laptop: Lenovo T60 Wireless: Intel 3945ABG Driver: ipw3945 1.2.0d (modinfo) Kernel: 2.6.18-92.el5 Steps to Reproduce: 1. Select ESSID from NetworkManager 2. Watch it spinning. Not even the first green ball lights up. 3. After a while it asks for the passphrase. 4. Type in passphrase. 5. Rinse, repeat. Actual results: No association. Expected results: Successful association. Additional info: Workaround is connect using wpa_supplicant from command line, which works perfectly on first try. Same laptop works perfectly with WEP encryption. Output of /var/log/messages during association: May 29 10:24:55 mteixeir dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason May 29 10:24:55 mteixeir NetworkManager: <information> Device eth1 activation scheduled... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) started... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting... May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1/wireless): access point 'homelinux' is encrypted, but NO valid key exists. New key needed. May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) New wireless user key requested for network 'homelinux'. May 29 10:24:55 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete. May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) New wireless user key for network 'homelinux' received. May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started... May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting... May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1/wireless): access point 'homelinux' is encrypted, and a key exists. No new key needed. May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'AP_SCAN 1' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'ADD_NETWORK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was '0' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 686f6d656c696e7578' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 proto WPA' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 psk <key>' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' May 29 10:25:03 mteixeir NetworkManager: <information> SUP: response was 'OK' May 29 10:25:03 mteixeir NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete. May 29 10:25:43 mteixeir NetworkManager: <information> Activation (eth1/wireless): association took too long (>40s), failing activation. May 29 10:25:43 mteixeir NetworkManager: <information> Activation (eth1) failure scheduled... May 29 10:25:43 mteixeir NetworkManager: <information> Activation (eth1) failed for access point (homelinux) May 29 10:25:43 mteixeir NetworkManager: <information> Activation (eth1) failed. May 29 10:25:43 mteixeir NetworkManager: <information> Deactivating device eth1. May 29 10:25:53 mteixeir NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / homelinux May 29 10:25:53 mteixeir NetworkManager: <information> Deactivating device eth1.
Is the AP set to broadcast it's SSID? Can you paste in the 'iwlist eth1 scan' output for your 'homelinux' AP?
I won't take my laptop home until the weekend. Will get your information as soon as possible.
Ok, paste it in when you have it.
Created attachment 321032 [details] Connect attemps from /var/log/messages Note that the first attempt was successful, but it could not get an IP from DHCP. I am pretty sure the DHCP server is fine, because it works perfectly if I connect the laptop to the LAN port of the wireless router.
Created attachment 321033 [details] iwlist
Created attachment 321034 [details] connection with wpa_supplicant wpa_supplicant connects fine, but I still can't get an IP from DHCP unless I add an statical IP with "ipconfig", then ping the DHCP server, then run "dhclient" (then it works).
Ok, that sounds more like a driver issue or a dhclient issue, not an NM issue. How are you running dhclient? Just "dhclient eth1"? Since you can ping the DHCP server, the encryption and wireless is all OK, it's either that the DHCP server isn't getting your packets, or you're not getting the DHCP server's replies, or the DHCP server ignores you. DO other machines work with the same DHCP server over wifi?
DHCP server is a Fedora 9 machine running dnsmasq. DHCP works fine for devices connected to the ethernet port of the wireless router (the server is connected via wireless), and even for this very same laptop when it is connected to the ethernet port. After I connect using wpa_supplicant, I simply run 'dhclient eth1'. It does not work at first. I need to ifconfig a fixed IP, ping the DHCP server, then 'dhclient eth1' works. Ping from server to client does not work if I set the IP using ifconfig. NetworkManager is able to connect to the wireless router after I 'service ipw3945d restart', but I still can't get DHCP. Yes, sounds like the ipw3945d or the daemon is failing, not NM per se. Can you move this ticket to the proper product?
Does another laptop or wireless card work with DHCP over wifi? We need to figure out whether this is the DHCP server not caring about requests from wireless, or whether it's really a driver issue...
This works for me on my laptop, which uses this driver. So I would really like to hear the answers to Dan's questions above. Also, we will have two drivers in 5.3 for this device - we are beginning to phase out the ipw3945 kmod and replace it with an in-kernel driver. If the problem persists I can provide some advice once RHEL5.3 ships about how to make the switch over to try that module instead. Jon.
This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release.
Sorry for not getting back before. I decided to update the wireless router firmware, and the problem describe on comment #6 does not happen anymore. I also have a Fedora Rawhire machine connected to the same wireless network just fine (using NM). Now, after firmware update, RHEL5 still refuses to connect using NM (stops on stage 2 of 5), even though wpa+dhclient works flawlessly 10 out ot 10 tries. Not even rmmoding and modprobing again work.
Please use the iwl3945 driver from now on.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Comment for future reference. Everything works well with RHEL 5.3.