Hi,
My wife has a new ASUS laptop with an Intel 3945 wireless card. I'm running CentOS 5 on all our desktops here (at work and at home), and I'm quite happy with it. I had a partial success in configuring the wireless card.
Basically I'm using [base], [updates], [extra] and [rpmforge] repos, configured with the yum-priorities plugin. Priority 10 for RPMForge, 1 for the others.
From RPMForge, I installed dkms-ipw3945, the driver for my wireless card. I gave it a first go with the most basic setup, that is: static IP, no encryption.
After installing the driver, the card shows up as eth1. I removed /etc/sysconfig/network-scripts/ifcfg-eth0 and edited a minimalistic ifcfg-eth1.
After a restart, the interface comes up OK, and I can connect to my access point as well as ping machines on the internet.
But now I'd like to install and use NetworkManager. I've read the according Wiki entry on the CentOS site. Here's what I did:
1) Added the 'NetworkManager' and 'NetworkManagerDispatcher' services (using chkconfig)
2) Removed the 'network' service (also using chkconfig)
3) Rebooted to be sure
Result:
1) The NetworkManager icon shows up OK on the upper right side of my GNOME desktop.
2) When an Ethernet cable is connected to the machine, NetworkManager configures a connection OK (cable connected to router).
3) The wireless ESSID of my access point shows up OK in NetworkManager. Ethernet cables get some sort of priority in NetworkManager, so I unplugged the cable and clicked on the wireless connection. NetworkManager tries to establish a connection for about 30 seconds, but fails.
... which leaves me clueless. Any suggestions?
Last detail: for the moment at least, I'm using no encryption at all on the access point. We live in a very remote place in the south French countryside, there's only hunters and wild boars around, so it's not a very friendly place for wlan-hackers :o)
Niki Kovacs
Niki Kovacs wrote: ...
... which leaves me clueless. Any suggestions?
Take a close look at what gets logged into /var/log/messages
Mogens
Mogens Kjaer a écrit :
Take a close look at what gets logged into /var/log/messages
Sorry couldn't try this out earlier, as my wife went away for a few days with the laptop.
Anyway, here goes. To try it out, I stopped the 'network' service and started 'NetworkManager' as well as 'NetworkManagerDispatcher'. Laptop was not connected to any Ethernet cable. My home access point showed up (essid 'zuhause', no encryption). I clicked on it to try to establish a connection:
--8<---------------------------------------------------------------- [root@nordinou init.d]# tail -f /var/log/messages Sep 3 16:32:39 nordinou NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / zuhause Sep 3 16:32:39 nordinou NetworkManager: <information> Deactivating device eth1. Sep 3 16:32:39 nordinou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason Sep 3 16:32:39 nordinou NetworkManager: <information> Device eth1 activation scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) started... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1/wireless): access point 'zuhause' is unencrypted, no key needed. Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'AP_SCAN 1' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'ADD_NETWORK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was '0' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 7a756861757365' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1/wireless): association took too long (>40s), failing activation. Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failure scheduled... Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failed for access point (zuhause) Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failed. Sep 3 16:33:19 nordinou NetworkManager: <information> Deactivating device eth1. --8<----------------------------------------------------------------
Now I was curious about this, so I tried it on another machine, my Buildbox, that also has a wireless card. Similar failure:
--8<---------------------------------------------------------------- [root@buildbox ~]# tail -f /var/log/messages Sep 3 16:35:52 buildbox dhcdbd: Started up. Sep 3 16:35:53 buildbox NetworkManager: <information> starting... Sep 3 16:35:53 buildbox NetworkManager: <WARNING> nm_system_device_get_system_config (): Network configuration for device 'wlan0' was invalid (non-DHCP configuration, but no gateway specified. Will use DHCP instead. Sep 3 16:35:53 buildbox NetworkManager: <information> wlan0: Device is fully-supported using driver 'rt61'. Sep 3 16:35:53 buildbox NetworkManager: <information> wlan0: driver does not support SSID scans (scan_capa 0x00). Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Sep 3 16:35:53 buildbox NetworkManager: <information> Now managing wireless (802.11) device 'wlan0'. Sep 3 16:35:53 buildbox NetworkManager: <information> Deactivating device wlan0. Sep 3 16:35:53 buildbox kernel: eth0: link down Sep 3 16:35:53 buildbox kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Sep 3 16:35:53 buildbox NetworkManager: <information> eth0: Device is fully-supported using driver '8139too'. Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Sep 3 16:35:53 buildbox NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'. Sep 3 16:35:53 buildbox NetworkManager: <information> Deactivating device eth0. Sep 3 16:35:53 buildbox NetworkManager: <information> Updating allowed wireless network lists. Sep 3 16:35:53 buildbox NetworkManager: <WARNING> nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored.. Sep 3 16:35:53 buildbox NetworkManager: <information> SWITCH: no current connection, found better connection 'eth0'. Sep 3 16:35:54 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Sep 3 16:35:54 buildbox NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link. Sep 3 16:35:54 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Sep 3 16:35:54 buildbox NetworkManager: <information> Will activate connection 'eth0'. Sep 3 16:35:54 buildbox NetworkManager: <information> Device eth0 activation scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) started... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) failure scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) failed. Sep 3 16:35:54 buildbox NetworkManager: <information> Deactivating device eth0. Sep 3 16:36:48 buildbox NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / zuhause Sep 3 16:36:48 buildbox NetworkManager: <information> Deactivating device wlan0. Sep 3 16:36:48 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason Sep 3 16:36:48 buildbox NetworkManager: <information> Device wlan0 activation scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) started... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0/wireless): access point 'zuhause' is unencrypted, no key needed. Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant ' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'AP_SCAN 2' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'ADD_NETWORK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was '0' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 7a756861757365' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0/wireless): association took too long (>20s), failing activation. Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failure scheduled... Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failed for access point (zuhause) Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failed. Sep 3 16:37:08 buildbox NetworkManager: <information> Deactivating device wlan0. --8<----------------------------------------------------------------
Any idea why NetworkManager refuses to connect to my network?
Niki
On Wed, Sep 3, 2008 at 7:55 AM, Niki Kovacs contact@kikinovak.net wrote:
Any idea why NetworkManager refuses to connect to my network?
Niki
If I remember, you are using the ipw3945 module. This is being deprecated and replaced by iwl3945. While the new one might not fix your problem, it wouldn't hurt to try it. In my case, ipw3945 did not work but iwl3945 did.
Trouble is that the iwl3945 module is disabled in the distro kernel. However, it is enabled in the centosplus kernel. So, the quickest way to test it is to install the cplus kernel.
Akemi
Akemi Yagi a écrit :
If I remember, you are using the ipw3945 module. This is being deprecated and replaced by iwl3945. While the new one might not fix your problem, it wouldn't hurt to try it. In my case, ipw3945 did not work but iwl3945 did.
Trouble is that the iwl3945 module is disabled in the distro kernel. However, it is enabled in the centosplus kernel. So, the quickest way to test it is to install the cplus kernel.
I figured that out late that night (early that morning?). I installed the centosplus kernel, and then I had to find an iwl3945-firmware package, otherwise the driver wouldn't work. I put it in my own repo:
http://download.tuxfamily.org/centos/5/os/i386/RPMS/iwl3945-firmware-2.14.1....
Suggestion: it would be a good idea to include this firmware package in the centosplus repo. This would spare some hassle.
Right now I'm running three different wireless cards on CentOS: Intel Pro 3945, Broadcom 4306 and Ralink 2561. Configuring each one of these reminded me of jumping through a series of burning loops.
Cheers!
Niki
On Thu, Sep 4, 2008 at 11:27 PM, Niki Kovacs contact@kikinovak.net wrote:
Akemi Yagi a écrit :
Trouble is that the iwl3945 module is disabled in the distro kernel. However, it is enabled in the centosplus kernel. So, the quickest way to test it is to install the cplus kernel.
I figured that out late that night (early that morning?). I installed the centosplus kernel, and then I had to find an iwl3945-firmware package, otherwise the driver wouldn't work. I put it in my own repo:
http://download.tuxfamily.org/centos/5/os/i386/RPMS/iwl3945-firmware-2.14.1....
Suggestion: it would be a good idea to include this firmware package in the centosplus repo. This would spare some hassle.
That will be really nice, yes. Another things would be to provide the iwl3945 module as kmod (or dkms). By the way, there is a newer version of the above firmware:
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-3945-ucode-15.28.1.6...
Akemi
On Wed, Sep 3, 2008 at 9:55 AM, Niki Kovacs contact@kikinovak.net wrote:
Mogens Kjaer a écrit :
Take a close look at what gets logged into /var/log/messages
Sorry couldn't try this out earlier, as my wife went away for a few days with the laptop.
Anyway, here goes. To try it out, I stopped the 'network' service and started 'NetworkManager' as well as 'NetworkManagerDispatcher'. Laptop was not connected to any Ethernet cable. My home access point showed up (essid 'zuhause', no encryption). I clicked on it to try to establish a connection:
--8<---------------------------------------------------------------- [root@nordinou init.d]# tail -f /var/log/messages Sep 3 16:32:39 nordinou NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / zuhause Sep 3 16:32:39 nordinou NetworkManager: <information> Deactivating device eth1. Sep 3 16:32:39 nordinou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason Sep 3 16:32:39 nordinou NetworkManager: <information> Device eth1 activation scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) started... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1/wireless): access point 'zuhause' is unencrypted, no key needed. Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'AP_SCAN 1' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'ADD_NETWORK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was '0' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 7a756861757365' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0'
Enabling something with a value of zero looks suspicious to me....
Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: response was 'OK' Sep 3 16:32:39 nordinou NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1/wireless): association took too long (>40s), failing activation. Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failure scheduled... Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failed for access point (zuhause) Sep 3 16:33:19 nordinou NetworkManager: <information> Activation (eth1) failed. Sep 3 16:33:19 nordinou NetworkManager: <information> Deactivating device eth1. --8<----------------------------------------------------------------
Now I was curious about this, so I tried it on another machine, my Buildbox, that also has a wireless card. Similar failure:
--8<---------------------------------------------------------------- [root@buildbox ~]# tail -f /var/log/messages Sep 3 16:35:52 buildbox dhcdbd: Started up. Sep 3 16:35:53 buildbox NetworkManager: <information> starting... Sep 3 16:35:53 buildbox NetworkManager: <WARNING> nm_system_device_get_system_config (): Network configuration for device 'wlan0' was invalid (non-DHCP configuration, but no gateway specified. Will use DHCP instead. Sep 3 16:35:53 buildbox NetworkManager: <information> wlan0: Device is fully-supported using driver 'rt61'. Sep 3 16:35:53 buildbox NetworkManager: <information> wlan0: driver does not support SSID scans (scan_capa 0x00). Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Sep 3 16:35:53 buildbox NetworkManager: <information> Now managing wireless (802.11) device 'wlan0'. Sep 3 16:35:53 buildbox NetworkManager: <information> Deactivating device wlan0. Sep 3 16:35:53 buildbox kernel: eth0: link down Sep 3 16:35:53 buildbox kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Sep 3 16:35:53 buildbox NetworkManager: <information> eth0: Device is fully-supported using driver '8139too'. Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Sep 3 16:35:53 buildbox NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Sep 3 16:35:53 buildbox NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'. Sep 3 16:35:53 buildbox NetworkManager: <information> Deactivating device eth0. Sep 3 16:35:53 buildbox NetworkManager: <information> Updating allowed wireless network lists. Sep 3 16:35:53 buildbox NetworkManager: <WARNING> nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored.. Sep 3 16:35:53 buildbox NetworkManager: <information> SWITCH: no current connection, found better connection 'eth0'. Sep 3 16:35:54 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Sep 3 16:35:54 buildbox NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link. Sep 3 16:35:54 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Sep 3 16:35:54 buildbox NetworkManager: <information> Will activate connection 'eth0'. Sep 3 16:35:54 buildbox NetworkManager: <information> Device eth0 activation scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) started... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) failure scheduled... Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:35:54 buildbox NetworkManager: <information> Activation (eth0) failed. Sep 3 16:35:54 buildbox NetworkManager: <information> Deactivating device eth0. Sep 3 16:36:48 buildbox NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / zuhause Sep 3 16:36:48 buildbox NetworkManager: <information> Deactivating device wlan0. Sep 3 16:36:48 buildbox dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason Sep 3 16:36:48 buildbox NetworkManager: <information> Device wlan0 activation scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) started... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0/wireless): access point 'zuhause' is unencrypted, no key needed. Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant ' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'AP_SCAN 2' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'ADD_NETWORK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was '0' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 7a756861757365' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' Sep 3 16:36:48 buildbox NetworkManager: <information> SUP: response was 'OK' Sep 3 16:36:48 buildbox NetworkManager: <information> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0/wireless): association took too long (>20s), failing activation. Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failure scheduled... Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failed for access point (zuhause) Sep 3 16:37:08 buildbox NetworkManager: <information> Activation (wlan0) failed. Sep 3 16:37:08 buildbox NetworkManager: <information> Deactivating device wlan0. --8<----------------------------------------------------------------
Any idea why NetworkManager refuses to connect to my network?
Niki
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Sep 3 16:32:39 nordinou NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' looks like it would disable the network?
-
Akemi Yagi -
Mogens Kjaer -
Niki Kovacs -
Rob Townley