#492531 network-manager-gnome: network-manager failed to connect invisible accesspoint

Package:
network-manager-gnome
Source:
network-manager-applet
Description:
network management framework (GNOME frontend)
Submitter:
Tobias
Date:
2011-10-14 13:15:06 UTC
Severity:
normal
#492531#5
Date:
2008-07-26 22:21:08 UTC
From:
To:
*** Please type your report below this line ***
information about access-point:

ssid= H3ll$gat3
encrypted= WPA-PSK

mode who fails:
network are invisible
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) started...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) scheduled...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) started...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) scheduled...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) complete.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) starting...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2/wireless):
access point 'H3ll$gat3' is encrypted, but NO
valid key exists.  New key needed.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) New
wireless user key requested for network
'H3ll$gat3'.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) complete.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) New
wireless user key for network 'H3ll$gat3' received.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) scheduled...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) started...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) scheduled...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 1
of 5 (Device Prepare) complete.
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) starting...
Jul 26 23:39:12 tlap NetworkManager: <info>  Activation (eth2/wireless):
access point 'H3ll$gat3' is encrypted, and a
key exists.  No new key needed.
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'INTERFACE_ADD
eth2^I^Iwext^I/var/run/wpa_supplicant^I'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'AP_SCAN 1'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'ADD_NETWORK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was '0'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'SET_NETWORK 0 ssid 48336c6c2467617433'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'SET_NETWORK 0 scan_ssid 1'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'SET_NETWORK 0 proto WPA'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'SET_NETWORK 0 psk <key>'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: sending command
'ENABLE_NETWORK 0'
Jul 26 23:39:13 tlap NetworkManager: <info>  SUP: response was 'OK'
Jul 26 23:39:13 tlap NetworkManager: <info>  Activation (eth2) Stage 2
of 5 (Device Configure) complete.
Jul 26 23:39:18 tlap NetworkManager: <info>  Old device 'eth2'
activating, won't change.
Jul 26 23:39:49 tlap last message repeated 6 times
Jul 26 23:40:09 tlap last message repeated 4 times
Jul 26 23:40:13 tlap NetworkManager: <info>  Activation (eth2/wireless):
association took too long (>60s), failing
activation.
Jul 26 23:40:13 tlap NetworkManager: <info>  Activation (eth2) failed
for access point (H3ll$gat3)
Jul 26 23:40:13 tlap NetworkManager: <info>  Activation (eth2) failed.
Jul 26 23:40:13 tlap NetworkManager: <info>  Deactivating device eth2.
Jul 26 23:40:13 tlap NetworkManager: <info>  Activation (eth2) failure
scheduled...
Jul 26 23:40:13 tlap NetworkManager: <WARN>  nm_signal_handler(): Caught
signal 11.  Generating backtrace...
Jul 26 23:40:13 tlap NetworkManager: ******************* START
**********************************
Jul 26 23:40:14 tlap NetworkManager: (no debugging symbols found)
Jul 26 23:40:14 tlap last message repeated 13 times
Jul 26 23:40:14 tlap NetworkManager: [Thread debugging using
libthread_db enabled]
Jul 26 23:40:14 tlap NetworkManager: [New Thread 0xb7b58720 (LWP 2691)]
Jul 26 23:40:14 tlap NetworkManager: [New Thread 0xb6b55b90 (LWP 3669)]
Jul 26 23:40:14 tlap NetworkManager: [New Thread 0xb7356b90 (LWP 2711)]
Jul 26 23:40:14 tlap NetworkManager: [New Thread 0xb7b57b90 (LWP 2707)]
Jul 26 23:40:14 tlap NetworkManager: (no debugging symbols found)
Jul 26 23:40:14 tlap last message repeated 7 times
Jul 26 23:40:14 tlap NetworkManager: 0xb7f79424 in __kernel_vsyscall ()
Jul 26 23:40:14 tlap NetworkManager: ******************* END
**********************************

.
.
.
.
and networkmanager crash



after reboot networkmanager works to same visible network

#492531#12
Date:
2008-08-03 23:21:46 UTC
From:
To:
tag -l10n
thanks

Please give some more details about this:

- can you run `lsmod` in a terminal so we know which network driver you
use? do you know the model of your card?
- does this happen ALWAYS when connecting to an invisible AP?
- are you only connecting to the wireless AP? You are not using VPN or
something else from NetworkManager?

thank you

#492531#19
Date:
2008-08-09 23:17:59 UTC
From:
To:
tag 492531 moreinfo
severity 492531 normal
thanks

Marking more info and downgrading to normal.

Please give us the requested info ;).

greetings

#492531#28
Date:
2011-10-14 13:12:32 UTC
From:
To:
This bug has been re-discovered in Debian Squeeze (6.0).

My home wifi is protected by WPA2 Personal and the SSID is not broadcasted. The
connection is marked with the checkmark "Allow all users to use this
connection" (or something along that line...).

Although it is possible to add the connection and stay connected, after a
reboot, any user will have to enter the root password in order to connect to
this wifi connection again.

Network manager applet doesn't show this connection in the list of
available (I would expect to remember this connection after I connect
once).

I think it is not correct to ask for root permission to connect to a hidden wifi
network.

If I make the access point to broadcast the SSID, everything works
fine, but for me this is a security issue, I want to be able to keep
the SSID hidden.

Thanks,