Intrepid Network Manager cannot connect to Hidden wireless networks

[aidave]

Binary package hint: network-manager

Can no longer connect to hidden wireless networks. Normal networks are still available.

Using Dell 1420n laptop with fresh install of Intrepid 64 bit.

Hidden wireless networks worked fine in Gutsy + Hardy.

[Aaron (a32ron)]

Dell 1520 with fresh install of Intrepid 32 bit. Won't connect to hidden network, but connects if I unhide the network.

[aidave (aidave)]

Interesting. We may have the same network card.

I tried installing WICD but it did not fix the issue, and in fact broke all networking, so I went back to the gnome network manager. Still cannot connect to hidden networks tho, which is frustrating because at work we use one.

[Roman Polach (rpolach)]

Do you use "Connect to Hidden Wireless Network" menu item in network manager?
Does it display some message after unsuccessful try to connect?

[aidave (aidave)]

This is now fixed for me due to whatever updates have come along.

[Aaron (a32ron)]

Mine still will not connect to a hidden network.

When trying to connect to a hidden network, it simply times out and asks
for the network password again. However, once I unhide the network, it
connects fine.

> This is now fixed for me due to whatever updates have come along.
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Fix Released
>
>

[aidave (aidave)]

Ok that sucks.
I will reopen it for you.

[Alexander Sack (asac)]

Aaron wrote:
> Mine still will not connect to a hidden network.
>
> When trying to connect to a hidden network, it simply times out and asks
> for the network password again. However, once I unhide the network, it
> connects fine.
>
>
>

please reproduce and attach your complete syslog taken after the timeout
error happens.

[Aaron (a32ron)]

Alexander Sack wrote:
> Aaron wrote:
>
>> Mine still will not connect to a hidden network.
>>
>> When trying to connect to a hidden network, it simply times out and asks
>> for the network password again. However, once I unhide the network, it
>> connects fine.
>>
>>
>>
>>
>
> please reproduce and attach your complete syslog taken after the timeout
> error happens.
>
>

Dec 29 09:40:05 Ubuntu810 syslogd 1.5.0#2ubuntu6: restart.
Dec 29 09:40:05 Ubuntu810 kernel: Inspecting
/boot/System.map-2.6.27-9-generic
Dec 29 09:40:05 Ubuntu810 kernel: Cannot find map file.
Dec 29 09:40:05 Ubuntu810 kernel: Loaded 72495 symbols from 105 modules.
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] Initializing cgroup
subsys cpuset
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] Initializing cgroup
subsys cpu
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] Linux version
2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008 (Ubuntu
2.6.27-9.19-generic)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-provided physical
RAM map:
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
0000000000000000 - 000000000009f000 (usable)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
000000000009f000 - 00000000000a0000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
0000000000100000 - 000000007fe92400 (usable)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
000000007fe92400 - 0000000080000000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000f4000000 - 00000000f8000000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000fec00000 - 00000000fec10000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000fed18000 - 00000000fed1c000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000fed20000 - 00000000fed90000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000feda0000 - 00000000feda6000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000fee00000 - 00000000fee10000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] BIOS-e820:
00000000fff00000 - 0000000100000000 (reserved)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] last_pfn = 0x7fe92
max_arch_pfn = 0x100000
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] kernel direct mapping
tables up to 38000000 @ 7000-c000
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] RAMDISK: 3781f000 -
37fefc5c
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] DMI 2.4 present.
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] ACPI: RSDP 000FBBF0,
0024 (r2 DELL )
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] ACPI: XSDT 7FE93E00,
005C (r1 DELL M08 27D70714 ASL 61)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] ACPI: FACP 7FE93C9C,
00F4 (r4 DELL M08 27D70714 ASL 61)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] ACPI: DSDT 7FE94400,
565E (r2 INT430 SYSFexxx 1001 INTL 20050624)
Dec 29 09:40:05 Ubuntu810 kernel: [ 0.000000] ACPI: FACS 7FEA2C00, 0040
Dec 29 09:40:05 Ubunt...

[Jan Weiher (jweiher)]

This affects me too.
I am using a broadcom onboard card with ndiswrapper - however, the same configuration worked fine with hardy.
I tried to use wicd too, but that did not help.
If someone needs some more information, i'll provide it.

[EmmaJane (emmajane)]

This is also a problem for me using the 9.04 Ubuntu Netbook Release on EEE PC 1000. I have no problems connecting to a visible network, but as soon as I hide the network (1) the connection is lost and (2) I cannot connect even when using the "Connect to Hidden Wireless Network..." wizard.

[Tony Espy (awe)]

Please re-test with Karmic Beta.

I've just done a bunch of testing of Karmic Beta + latest updates and had no issues with hidden networks.

If you still have a failure with Karmic Beta + latest, then please use the command:

apport-collect 294175

...to add additional information to the bug that'd help us debug.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[fb (fb-adimit)]

Hi,

I just installed Ubuntu 11.04 from scratch. I tried to connect to my wireless network WPA&WPA2 Personal, hidden network and it failed. When 'unhiding' the network, it connects without any problem. After hiding during the network being active it remains active.

After disabling wireless and enabling wireless (in the mean time connected to another network) it can not connect anymore.

The syslog shows messages like:
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) starting connection 'fb'
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0/wireless): access point 'fb' has security, but secrets are required.
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0/wireless): connection 'fb' has security, and secrets exist. No new secrets needed.
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Config: added 'ssid' value 'fb'
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Config: added 'scan_ssid' value '1'
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Config: added 'psk' value '<omitted>'
Apr 29 14:32:25 fbdb NetworkManager[766]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 29 14:32:25 fbdb NetworkManager[766]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 29 14:32:25 fbdb NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (De...