[opensuse-factory] NetworkManager: <WARN> Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash
Hello all ################################ # wifi connection problem ################################ I installed Beta 1 DVD on T60 Thinkpad, Core Duo Post boot my wifi Essid "Mercury" (wlan0) WPA connection is KO using an Intel Wifi(3945abg) card ################################ # My analyse ################################ dmesg states "wlan0: disassociate(reason=3)" which means "Station has left the basic service area or extended service area and is deauthenticated". Why is this error happening at this point ? IMHO NetworkNetworkManger log suggests that the reason is that NetworkManager "Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.." More details follow... ################################ # dmesg gives ################################ ADDRCONF(NETDEV_UP): wlan0: link is not ready NET: Registered protocol family 17 wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:17:33:98:2c:3c wlan0: RX authentication from 00:17:33:98:2c:3c (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:17:33:98:2c:3c wlan0: RX AssocResp from 00:17:33:98:2c:3c (capab=0x401 status=0 aid=1) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:17:33:98:2c:3c) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:17:33:98:2c:3c wlan0: RX authentication from 00:17:33:98:2c:3c (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:17:33:98:2c:3c wlan0: RX AssocResp from 00:17:33:98:2c:3c (capab=0x401 status=0 aid=1) wlan0: associated wlan0: disassociate(reason=3) wlan0: disassociate(reason=3) ################################ # dmesg analyse ################################ "wlan0: disassociate(reason=3)" means "Station has left the basic service area or extended service area and is deauthenticated". Why is this error happening at this point ? NetworkManger log would suggests that the reason is that NetworkManager "Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.." ################################ NetworkManger log on boot lists ################################ NetworkManger log on boot lists Apr 22 19:28:38 linux NetworkManager: <info> Trying to start the system settings daemon... Apr 22 19:28:42 linux NetworkManager: <info> Bringing up device eth0 Apr 22 19:28:42 linux NetworkManager: <info> Deactivating device eth0. Apr 22 19:28:42 linux NetworkManager: <info> Bringing up device wlan0 Apr 22 19:28:42 linux NetworkManager: <info> Deactivating device wlan0. Apr 22 19:28:42 linux NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1). Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) starting connection 'System Mercury (wlan0)' Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 22 19:28:44 linux NetworkManager: <info> (wlan0) Supplicant interface state change: 1 -> 4 Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0/wireless): access point 'System Mercury (wlan0)' has security, but secrets are required. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 22 19:28:44 linux NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) failed for access point (Mercury) Apr 22 19:28:44 linux NetworkManager: <info> Marking connection 'System Mercury (wlan0)' invalid. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) failed. Apr 22 19:28:44 linux NetworkManager: <info> Deactivating device wlan0. ############### # Other info ############### linux:~ # uname -a Linux linux 2.6.25-rc9-17-pae #1 SMP 2008-04-15 22:54:53 +0200 i686 i686 i386 GNU/Linux linux:~ # lsmod | grep 3945 iwl3945 108504 0 firmware_class 25984 3 microcode,pcmcia,iwl3945 mac80211 238820 1 iwl3945 led_class 21764 1 iwl3945 cfg80211 43784 2 iwl3945,mac80211 lspci | grep -i 3945 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) rpm -qa | grep -i Net | sort NetworkManager-0.7.0.r3556-4 NetworkManager-glib-0.7.0.r3556-4 NetworkManager-kde-0.7r795810-5 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
IMHO NetworkNetworkManger log suggests that the reason is that NetworkManager "Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.."
The issue is with the suse specific system settings loader: it tries to use the wireless information stored in yast configuration files and does it incompletely. I am working on fixing this, but to get things going, use the "Connect to Other Wireless Network..." dialog in the applet to manually create a new connection. Tambet --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
James PEARSON
-
Tambet Ingo