11.2 Hidden SSID

English Network/Internet
21

should being the keyword there.
I turned visibility back on and created a profile and could get on line fine. Then I turned visibility off and NetworkManager sat on “activating” for a long time. So I recreated a profile and did a SSID scan and it found the network. That profile could not connect either.
the log output:

Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Activation (wlan0/wireless): connection 'New Wireless Connection' requires no security.  No secrets needed.                                                                  
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Config: added 'ssid' value '3springsfarm'                    
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Config: added 'scan_ssid' value '1'                          
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'                        
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  Config: set interface ap_scan to 1                           
Jan  1 09:34:47 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jan  1 09:34:48 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jan  1 09:34:58 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Jan  1 09:34:58 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jan  1 09:34:59 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jan  1 09:35:09 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Jan  1 09:35:09 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jan  1 09:35:10 linux-7098 NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  Activation (wlan0/wireless): association took too long, failing activation.
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  (wlan0): device state change: 5 -> 9 (reason 11)
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  Activation (wlan0) failed for access point (3springsfarm)
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  Marking connection 'New Wireless Connection' invalid.
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  Activation (wlan0) failed.
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  (wlan0): device state change: 9 -> 3 (reason 0)
Jan  1 09:35:12 linux-7098 NetworkManager: <info>  (wlan0): deactivating device (reason: 0).

The log was the same for both profiles.

22

So the good news is we are making progress :slight_smile: the bad news I really don’t know why it’s not working now. The key point hovewer is to not recreate a profile once in works :slight_smile: so that openSUSE somehow trusts this connection. Please try the procedure of unhiding and hiding again and this time leave the profile. Also don’t delete it ever :slight_smile: Leave the working profile all alone. Once you hide the network try out this command :

/etc/init.d/network restart

Of course follow the NetworkManager log all the time with the previous tail -f command and report back where this will get You.

Also be sure to check your knetworkmanager ways of storing secrets. It should be set to what is on the screenshot. http://sunum.kt.agh.edu.pl/~glistwa/knetworkmanager_storing_secrets
The phrase surrounded by red in English should say something like “Storing secrets of the connection : In a safe place (cyphered)”. And be sure also to enable unconditional access of knetworkmanager to kwallet.

Best regards,
Greg

23

I didn’t delete the profile, I tried everything I could to get it working, then created a new profile afterwards, neither were deleted. I created a third profile to check the unhide/hide restart cycle. It still failed, and the logs were the same. I did not realize how important the “-f” in tail is :wink:

And it doesn’t seem like the kwallet access would be important, but it is set to unlimited or something to that extent.

24

Sorry to hear that. I just ran out of ideas what else might You try. Hopefully someone else will check on this thread and five You some better advice. Good luck :slight_smile:

Best regards,
Greg

25

Alright, thanks.