GNOME Bugzilla – Bug 541816
Can't create new wireless network
Last modified: 2008-07-08 17:40:59 UTC
I am trying to create a new wireless network (particularly, with no encryption for starters) with the gnome applet. However, I just get the message "Trying to connect to wireless network «(null)»" (nm 0.6.6-0ubuntu5) or "Trying to connect to wireless network «MyChosenSSID»" (nm 0.7~~svn20080703t022721+eni1-0ubuntu0~pre0) . Then, after a couple of minutes or so, it gets back to the previously used connection and no new wireless connection is created. I am using Ubuntu Hardy, using both the included 0.6.6 version as well as a PPA-provided 0.7-svn snapshot. I have been trying since Dapper (June 2006), with any success. The relevant syslog-messages from Network Manager are: Using nm 0.7: Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): device state change: 8 -> 3 Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): deactivating device. Jul 7 01:36:42 motin-laptop NetworkManager: <info> wlan0: canceled DHCP transaction, dhclient pid 8297 Jul 7 01:36:42 motin-laptop kernel: [ 1084.979954] wlan0: disassociate(reason=3) Jul 7 01:36:42 motin-laptop NetworkManager: <info> Clearing nscd hosts cache. Jul 7 01:36:42 motin-laptop NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Missing link name TLV (errn o = Invalid argument) Jul 7 01:36:42 motin-laptop avahi-daemon[5691]: Withdrawing address record for 192.168.1.5 on wlan0. Jul 7 01:36:42 motin-laptop avahi-daemon[5691]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.5. Jul 7 01:36:42 motin-laptop avahi-daemon[5691]: Interface wlan0.IPv4 no longer relevant for mDNS. Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) starting connection 'Motin' Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 0 Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0/wireless): connection 'Motin' requires no security. No secrets needed. Jul 7 01:36:42 motin-laptop NetworkManager: <info> Config: added 'ssid' value 'Motin' Jul 7 01:36:42 motin-laptop NetworkManager: <info> Config: added 'mode' value '1' Jul 7 01:36:42 motin-laptop NetworkManager: <info> Config: added 'frequency' value '2462' Jul 7 01:36:42 motin-laptop NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Jul 7 01:36:42 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 7 01:36:42 motin-laptop NetworkManager: <info> Config: set interface ap_scan to 2 Followed by repeated: Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2 Jul 7 01:36:42 motin-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3 Jul 7 01:36:45 motin-laptop kernel: [ 1087.428505] wlan0: Initial auth_alg=0 Jul 7 01:36:45 motin-laptop kernel: [ 1087.428509] wlan0: authenticate with AP 00:00:00:00:00:00 Jul 7 01:36:45 motin-laptop kernel: [ 1087.627925] wlan0: authenticate with AP 00:00:00:00:00:00 Jul 7 01:36:46 motin-laptop kernel: [ 1087.772864] wlan0: authenticate with AP 00:00:00:00:00:00 Jul 7 01:36:46 motin-laptop kernel: [ 1087.899682] wlan0: authentication with AP 00:00:00:00:00:00 timed out Jul 7 01:36:47 motin-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0 Ending in: ... Jul 7 01:37:02 motin-laptop kernel: [ 1099.050512] wlan0: authentication with AP 00:00:00:00:00:00 timed out Jul 7 01:37:07 motin-laptop NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation. Jul 7 01:37:07 motin-laptop NetworkManager: <info> (wlan0): device state change: 5 -> 9 Jul 7 01:37:07 motin-laptop NetworkManager: <info> Activation (wlan0) failed for access point (Motin) Jul 7 01:37:07 motin-laptop NetworkManager: <info> Marking connection 'Motin' invalid. Jul 7 01:37:07 motin-laptop NetworkManager: <info> Activation (wlan0) failed. Jul 7 01:37:07 motin-laptop NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jul 7 01:37:07 motin-laptop NetworkManager: <info> (wlan0): deactivating device. Using nm 0.6.6: Jun 28 17:59:01 motin-laptop NetworkManager: <info> Creating network 'motin-laptop' on device '/org/freedesktop/NetworkManager/Devices/wlan0'. Jun 28 17:59:01 motin-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason Jun 28 17:59:01 motin-laptop NetworkManager: <info> Device wlan0 activation scheduled... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) started... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 28 17:59:01 motin-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'motin-laptop' is unencrypted, no key needed. Jun 28 17:59:03 motin-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1) Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 2' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was '0' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 6d6f74696e2d6c6170746f70' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 mode 1' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 frequency 2412' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Jun 28 17:59:03 motin-laptop NetworkManager: <info> SUP: response was 'OK' Jun 28 17:59:03 motin-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Followed by repeated: Jun 28 18:00:20 motin-laptop kernel: [11976.775999] wlan0: Initial auth_alg=0 Jun 28 18:00:20 motin-laptop kernel: [11976.776011] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:21 motin-laptop kernel: [11976.909591] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:21 motin-laptop kernel: [11977.026622] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:21 motin-laptop kernel: [11977.141840] wlan0: authentication with AP 00:00:00:00:00:00 timed out Jun 28 18:00:23 motin-laptop kernel: [11978.661601] wlan0: Initial auth_alg=0 Jun 28 18:00:23 motin-laptop kernel: [11978.661606] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:23 motin-laptop kernel: [11978.836640] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:24 motin-laptop kernel: [11979.026279] wlan0: authenticate with AP 00:00:00:00:00:00 Jun 28 18:00:24 motin-laptop kernel: [11979.226240] wlan0: authentication with AP 00:00:00:00:00:00 timed out Jun 28 18:00:25 motin-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change. Ending in: Jun 28 18:01:03 motin-laptop NetworkManager: <info> Activation (wlan0/wireless): association took too long (>120s), failing activation. Jun 28 18:01:03 motin-laptop NetworkManager: <info> Activation (wlan0) failure scheduled... Jun 28 18:01:03 motin-laptop NetworkManager: <info> Activation (wlan0) failed for access point (motin-laptop) Jun 28 18:01:03 motin-laptop NetworkManager: <info> Activation (wlan0) failed. Jun 28 18:01:03 motin-laptop NetworkManager: <info> Deactivating device wlan0. It is clearly not setting up a correct Ad-Hoc AP, since 00:00:00:00:00:00 definitely looks like an invalid address... Note about hardware: On my old laptop using ipw2200 (on which I haven't watched the messages log during an attempt), it could be related to the hardware (Bug https://bugs.launchpad.net/bugs/75358). This time, it is however a clean install of Hardy on an XPS M1330 using the Santa Rosa Intel Wireless Chipset (unsure of which one it is but someone mentioned chipset Intel 4965 AGN on http://ubuntuforums.org/showthread.php?t=743660). Again, creating new networks hasn't worked once for me since 2006. This citation really got my hopes up for 0.7: > For once you’ll be able to easily share that $9.99/hr hotel WiFi > connection with your friends over ethernet, or an ethernet connection > with your friends over WiFi. http://blogs.gnome.org/dcbw/2007/10/15/networkmanager-07-is-the-new-chuck-norris/ But this requires being able to create Ad Hoc wireless networks, doesn't it?
Created attachment 114090 [details] My output of "sudo lshw -class network"
It likely doesn't work because there are fixes required for your card for both wpa_supplicant and the mac80211 kernel 802.11 stack. wpa_supplicant: [PATCH] wpa_supplicant: give adhoc associations a bit more time [PATCH v2] wext: handle mode switches correctly for mac80211 kernel (wireless-testing.git): 872ba53395b2a8be08c3ea2d39e225e5b4a8cb40 mac80211: decrease IBSS creation latency 507b06d0622480f8026d49a94f86068bb0fd6ed6 mac80211: send association event on IBSS create you'll need all 4 of these before NetworkManager (either 0.6 or 0.7) can create adhoc networks with any mac80211-based drivers. Note that some mac80211-based drivers (zd1211 for example) cannot yet do IBSS/adhoc mode at all.
Thank you very much for your informative reply! According to this, one would need a 2.6.25.6+ kernel and wpa_supplicant at least 0.6.3-2 as these versions have incorporated the mentioned patches. More info about this bug (which is now correctly reported against linux & wpasupplicant instead of network-manager thanks to your comment) as well as instructions on how to install the above versions in Ubuntu Hardy can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/183303
For ipw2200, you'll also want: ipw2200: expire and use oldest BSS on adhoc create a6d4eae80157830af9c9d80de2daf6611696a34e otherwise in some situations an ipw2200 card will never create the adhoc network.