Re: networkmanager fails to associate (ipw3945)
Usamah Malik wrote: This is with regards to a thread you started on networkmanager list regarding networkmanager not associating. I have been having the same exact issue was wondering what did you do to resolve it. I am using 2.6.19-2911 kernel + ipw3945 + NetworkManager it fails to establish connection to my WPA enabled wlan. It is however able to show (but not connect) to wlans in the neibourhood. Any pointers are appreciated. as you can see in the thread there seems to be no soultion for it and the discussion stopped :( the only solution that I can tell you is to use wpa_supplicant directly, networkmanager seems not to work with ipw3945 + wpa. it seems to me that in is not working with ipw3945 period. I have the same problem but with an open AP. Would like a resolution though :) Thanks, Sami ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM -- does it actually work?
ok.. I took Ryan's advice and ran NM with --no-daemon... and without wpa_supplicant as suggested. It fails to associate to the AP when it's already associated.. thus getting stuck and... making me hit walls with my head :) This is the output: NM: information eth1: Device is fully-supported using driver 'ipw3945'. NM: information nm_device_init(): waiting for device's worker thread to start NM: information nm_device_init(): device's worker thread started, continuing. NM: information Now managing wireless (802.11) device 'eth1'. NM: information Deactivating device eth1. NM: information eth0: Device is fully-supported using driver 'tg3'. NM: information nm_device_init(): waiting for device's worker thread to start NM: information nm_device_init(): device's worker thread started, continuing. NM: information Now managing wired Ethernet (802.3) device 'eth0'. NM: information Deactivating device eth0. NM: information Updating allowed wireless network lists. NM: WARNINGnm_dbus_get_networks_cb (): error received: org.freedesktop.NMInfo.NoNetworks - There are no wireless networks stored.. NM: debug info[1172262737.561285] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'opennet' NM: information User Switch: /org/freedesktop/NM/Devices/eth1 / opennet NM: information Deactivating device eth1. NM: information Device eth1 activation scheduled... NM: information Activation (eth1) started... NM: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NM: information Activation (eth1) Stage 1 of 5 (Device Prepare) started... NM: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... NM: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete. NM: information Activation (eth1) Stage 2 of 5 (Device Configure) starting... NM: information Activation (eth1/wireless): access point 'opennet' is unencrypted, no key needed. NM: information SUP: sending command 'INTERFACE_ADD eth1 wext/var/run/wpa_supplicant ' NM: information SUP: response was 'OK' NM: information SUP: sending command 'AP_SCAN 1' NM: information SUP: response was 'OK' NM: information SUP: sending command 'ADD_NETWORK' NM: information SUP: response was '0' NM: information SUP: sending command 'SET_NETWORK 0 ssid 6f70656e6e6574' NM: information SUP: response was 'OK' NM: information SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' NM: information SUP: response was 'OK' NM: information SUP: sending command 'ENABLE_NETWORK 0' NM: information SUP: response was 'OK' NM: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. NM: information Activation (eth1/wireless): association took too long (40s), failing activation. NM: information Activation (eth1) failed for access point (opennet) NM: information Activation (eth1) failure scheduled... NM: information Activation (eth1) failed. NM: information Deactivating device eth1. sendmsg(CTRL_IFACE monitor): No such file or directory maybe someone saw this before... Adrian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM -- does it actually work?
On Fri, 2007-02-23 at 15:56 -0500, Ryan Novosielski wrote: 6f70656e6e6574' actually that's hexa for 'opennet' ... and the same happens after a reboot ... still hanging... thinking it doesn't associate to the AP Adrian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM -- does it actually work?
On Sat, 2007-02-24 at 00:43 +0200, Adrian Vasile wrote: On Fri, 2007-02-23 at 15:56 -0500, Ryan Novosielski wrote: 6f70656e6e6574' actually that's hexa for 'opennet' ... and the same happens after a reboot ... still hanging... thinking it doesn't associate to the AP In a brilliant fashion, I discovered that actually it's wpa_supplicant's fault.. while asking NM to connect to my AP, I used wpa_cli to connect and see what it's actually trying to do. Here's the result: 2Trying to associate with 00:0f:66:57:20:8a (SSID='opennet' freq=0 MHz) 2Authentication with 00:00:00:00:00:00 timed out. 2Trying to associate with 00:0f:66:57:20:8a (SSID='opennet' freq=0 MHz) 2CTRL-EVENT-TERMINATING - signal 15 received The signal is given after 40s of timeout by NM. Being new to this NM/wpa_supplicant I ask, is this how it's supposed to connect? Cause the only problematic thing here is that wpa_s doesn't know on which freq it should connect (although it knows even my AP mac address). Anybody has any ideas about this? And secondly, which is better.. to run a separate instance of wpa_supplicant along side NM or let NM run it's own instance (anyway it does that) and it doesn't connect to the first wpa daemon's control socket. Thank you, Adrian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
