WIFI SSID does not show in GUI, But does in IWLIST 12.2

English Network/Internet
1

Upgraded to Opensuse 12.2 from 11.4 (I did not have this issue with 11.4) - My SSID shows in iwlist as FBI (renamed as I thought it may be related to my ssid being all numbers). Connection does not show in network manager (GUI), if I click on hidden network, and type in the ssid & passsword, it connects fine. (other than showing multiple instances that I need to delete every so often). My sons phone shows & connects fine everytime, as does his win7 laptop. My laptop(Hewlett-Packard Compaq Presario CQ60 Notebook) connected fine prior to upgrade to 12.2. My router is a linksys e4200 (at latest firmware). I have tried reinstalling 12.2, but lost my 11.4 disc, so I connot go back.

Any help is appreciated. Thanks
John Kilbert

my card: (from lspci)
07:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)

DMSG: (i took ut some data seeming unimportant or potentially identifying)
15.926937] ath5k phy0: Atheros AR2425 chip found (MAC:
25.972968] ADDRCONF(NETDEV_UP): eth0: link is not ready
26.098983] ADDRCONF(NETDEV_UP): wlan0: link is not ready
325.052052] wlan0: authenticate with
325.062425] wlan0: send auth to (try 1/3)
325.063914] wlan0: authenticated
325.074242] wlan0: associate with (try 1/3)
325.076610] wlan0: RX AssocResp from (capab=0x411 status=0 aid=2)
325.077513] wlan0: associated
325.077844] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
327.095424] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=ff:fe8d:4d2e DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
331.164783] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
331.172151] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
334.088956] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
336.006548] wlan0: no IPv6 routers present
342.082751] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC= DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
358.068754] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC= DST=LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
390.030510] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
453.954711] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
581.824425] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC= DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
837.592067] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC= DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
1348.945894] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC= DST= LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44

driver: ath5k.

linux-1ln4:/home/kil566 # iwlist wlan0 scan
wlan0     Scan completed :                                                                                                                                              
          Cell 01 - Address: 58:6D:8F:38:F7:74                                                                                                                          
                    Channel:1                                                                                                                                           
                    Frequency:2.412 GHz (Channel 1)                                                                                                                     
                    Quality=56/70  Signal level=-54 dBm                                                                                                                 
                    Encryption key:on                                                                                                                                   
                    ESSID:"FBI"                                                                                                                                         
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s                                                                                                
                              24 Mb/s; 36 Mb/s; 54 Mb/s                                                                                                                 
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 28ms ago
                    IE: Unknown: 0003464249
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030101
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: 2D1AFC181BFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1601080000000000000000000000000000000000000000
                    IE: Unknown: DD7F0050F204104A00011010440001021041000100103B000103104700109BD84EA601A44639AA999336D82E8CA010210005436973636F1023000D4C696E6B7379732045343230301024000776312E302E30311042000234321054000800060050F20400011011000D4C696E6B737973204534323030100800020084103C000103
                    IE: Unknown: DD090010180200F02C0000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
          Cell 02 - Address: 00:22:75:49:CF:3F
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=33/70  Signal level=-77 dBm  
                    Encryption key:on
                    ESSID:"L. Murphy WiFi Network"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000002ed43b81cc
                    Extra: Last beacon: 8329ms ago
                    IE: Unknown: 00164C2E204D75727068792057694669204E6574776F726B
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030106
                    IE: Unknown: 32040C183060
                    IE: Unknown: 0706555320010B10
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown: DD0E0050F204104A0001101044000102
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0104
                    IE: Unknown: 2D1AEE1117FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown: 3D1606070000000000000000000000000000000000000000
                    IE: Unknown: 7F0101
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05000035127A
                    IE: Unknown: DD1E00904C33EE1117FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown: DD1A00904C3406070000000000000000000000000000000000000000
                    IE: Unknown: DD07000C4304000000
          Cell 03 - Address: 4C:60:DE:3E:CF:14
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=29/70  Signal level=-81 dBm  
                    Encryption key:on
                    ESSID:"DaisyandBill"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000014dab6eb62
                    Extra: Last beacon: 389ms ago
                    IE: Unknown: 000C4461697379616E6442696C6C
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: 2D1A6C181BFF00000000000000000000000000000000000000000000
                    IE: Unknown: 3D1606081100000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: Unknown: DD7F0050F204104A00011010440001021041000100103B000103104700104FE40B330CADB5945B05050BF891AE581021000D4E4554474541522C20496E632E10230009574E5231303030763310240009574E523130303076331042000538333235381054000800060050F204000110110009574E52313030307633100800020084
                    IE: Unknown: DD090010180200F0050000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: DD1E00904C336C181BFF00000000000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C3406081100000000000000000000000000000000000000

Graphically- does not show in network manager:

http://i.imgur.com/KYl1c.png

Clicking “hidden network” and typng the ssid & password, it connects fine.

http://i.imgur.com/yYa2n.png

2

If you configure the connection for “System Connection” and “Connect automatically” it will probably work fine.

This is one of the changes to NetworkManager since 11.4.

As I recall, “System connection” was grayed out in 11.4.

3

I can confirm once you go into the “Manage Connections” and check the check box’s for “System Connection” or something along those lines, My MacBook picks up my router and connects right from waking up from a cold boot and suspend/hibernate.

4

I tried checking the system connection box, and it did save the connection and reconnect. So, thanks to you guys for the help!
While this fixes my connection issue, I still do not understand why it shows as hidden, and why this fixes it. Seems like a bug.

5

I suppose you have seen something similar to what I had with four different laptops. I use KDE. All laptops have undergone distribution upgrade with zypper dup. First from openSUSE 11.4 to 12.1 and recently to 12.2. All seemed to miss the default AP after boot. If I disable and re-enable wireless either in the network applet or by a hardware switch the default AP appears and a connection is established automatically.

It seems the key file got corrupt at some point of time and it cannot be corrected with KDE-tools. At least I have not figured out how. The Network log shows that NetworkManager actually tries to connect to the default AP (connect automatically AP to be more precise). NetworkManager does not get access to the WPA-key and therefore disables and removes this AP entry. I have no idea why connection succeeds after I bring wireless down and up again.

In this case my fix was to use nm-connection-editor which is a gnome user interface for Networkmanager. I deleted all entries and entered my default AP with the WPA-key. After this I get an automatic connection with my default AP after boot.

Here are some extracts from the NetworkManager log (I deleted lines in between to keep the listing shortish):

Sep 21 18:29:20 computer1 NetworkManager[819]: <info> Auto-activating connection 'WlanNet'.
....
Sep 21 18:29:20 computer1 NetworkManager[819]: <info> Activation (wlan0/wireless): access point 'WlanNet' has security, but secrets are required.
----
Sep 21 18:29:20 computer1 NetworkManager[819]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Sep 21 18:29:20 computer1 NetworkManager[819]: <warn> Activation (wlan0) failed for access point (WlanNet)
Sep 21 18:29:20 computer1 NetworkManager[819]: <info> Marking connection 'WlanNet' invalid.
Sep 21 18:29:20 computer1 NetworkManager[819]: <warn> Activation (wlan0) failed.

=============================

## Disable and re-enable wireless in NetworkManager applet

=============================

Sep 21 18:33:53 computer1 NetworkManager[819]: <info> WiFi hardware radio set disabled
Sep 21 18:33:53 computer1 NetworkManager[819]: <info> WiFi now disabled by radio killswitch
Sep 21 18:33:56 computer1 NetworkManager[819]: <info> (wlan0): bringing up device.
Sep 21 18:33:56 computer1 NetworkManager[819]: <info> WiFi hardware radio set enabled
Sep 21 18:33:56 computer1 NetworkManager[819]: <info> WiFi now enabled by radio killswitch
Sep 21 18:33:56 computer1 NetworkManager[819]: <info> (wlan0): bringing up device.
----
Sep 21 18:33:57 computer1 NetworkManager[819]: <info> Activation (wlan0) starting connection 'WlanNet'
----
Sep 21 18:33:57 computer1 NetworkManager[819]: <info> Activation (wlan0/wireless): connection 'WlanNet' has security, and secrets exist.  No new secrets needed.
----
Sep 21 18:34:05 computer1 NetworkManager[819]: <info> (wlan0): DHCPv4 state changed preinit -> bound

==============================

## Edit NetworkManager settings with nm-connection-editor and reboot

==============================

Sep 21 18:45:33 computer1 NetworkManager[747]: <info> NetworkManager (version 0.9.4.0) is starting...
Sep 21 18:45:33 computer1 NetworkManager[747]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
----
Sep 21 18:45:33 computer1 NetworkManager[747]:    keyfile: parsing WlanNet ...
Sep 21 18:45:33 computer1 NetworkManager[747]:    keyfile:     read connection 'WlanNet'
----
Sep 21 18:45:33 computer1 NetworkManager[747]: <info> WiFi enabled by radio killswitch; enabled by state file
----
Sep 21 18:45:33 computer1 NetworkManager[747]: <info> Networking is enabled by state file
----
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> (wlan0): bringing up device.
----
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> Activation (wlan0/wireless): connection 'WlanNet' has security, and secrets exist.  No new secrets needed.
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> Config: added 'ssid' value 'WlanNet'
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> Config: added 'scan_ssid' value '1'
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Sep 21 18:45:34 computer1 NetworkManager[747]: <info> Config: added 'psk' value '<omitted>'
----
Sep 21 18:45:37 computer1 NetworkManager[747]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
----

Sep 21 18:45:39 computer1 NetworkManager[747]: <info> Activation (wlan0) successful, device activated.
6

Well, I have to correct my previous post above. Using nm-connetion-editor does not help either other than maybe making it marginally easier to set the System Connection bit. Maybe this has something to do with the order things are brought up? Is there something that should already be running, but is not at the time NetworkManager makes the first attempt to establish the connection? This would explain the success after one brings wireless down and up. The latter is needed in order for NetworkManager to reinitialize its list of APs. Maybe I will investigate this if and when I have more time.

7

On 09/21/2012 12:36 PM, GirlGeek wrote:
>
> Well, I have to correct my previous post above. Using
> nm-connetion-editor does not help either other than maybe making it
> marginally easier to set the System Connection bit. Maybe this has
> something to do with the order things are brought up? Is there something
> that should already be running, but is not at the time NetworkManager
> makes the first attempt to establish the connection? This would explain
> the success after one brings wireless down and up. The latter is needed
> in order for NetworkManager to reinitialize its list of APs. Maybe I
> will investigate this if and when I have more time.

If your database, or the wallet used to store the secrets, is damaged, you can
use the KDE connection manager to delete all stored connections, and then add
them back. That works for me. None of mine are system connections, and none are
automatically selected, but those details should not matter.

8

I do not use in this case kwallet for AP passwords. I did a little further study. When I select a system connection the WPA- key data is stored in a system file which is available to NetworkManager at all times. This is why a system connection work.

When I set the connection not to be a system connection the data is stored individually for me and eventually for each user that uses the same AP. This info only becomes available to NetworkManager at a certain point of time after the user initiates his or her individual KDE-session either by auto login or by manual login.

Unfortunately NetworkManager tries to establish a connection too early and does not get access to the WPA-key. The connection fails and NetworkManagager invalidates the AP. This is why it does not show in the list of available APs. NetworkManager will not try again an invalidated AP unless something external triggers this. Such a trigger can be switching off and on wireless in the Network-applet, using a hardware switch for the same effect or even restarting NetworkManager. All work.

So either NetworkManager tries to establish a connection too early or KDE fails to provide the key in time. Kwallet may indeed play a role in this depending on in which order the keys are searched for.

If actually matters whether you mark a connection a system connection since the information is stored differently and is therefore available for NetworkManager early on. It also matters whether you mark a connection automatic since if there are no automatic connections KDE will have plenty of time to initiate all necessary services and there should not be any reason for NetworkManager to fail because of this timing issue.

So it seems there is a need for further study. Please feel free to share the burden. Is this a bug? Well at least things do not work as one would expect them to work.

9

My primary wireless connection at home is configured as a ‘System connection’, and also ‘Connect automatically’. I’m using kwallet to store the pass-phrase, and it is always up and running before the desktop is up and running. I have my laptop configured to do the same for my work wireless connection.

10

You will probably find that the pass phrase is actually in a file in “/etc/NetworkManager/system-connections” (that file is only readable by root).

11

Yes and no. Yes if you set up a system connection.

12

So finally here is a quick and dirty fix.

In order to get automatic connection in kde even when you do not set up your connection as a system connection put this little script in ~.kde4/Autostart and make it executable.

#!/bin/bash
# A temporary fix 
/usr/bin/nmcli nm wifi off > /dev/null
/usr/bin/nmcli nm wifi on  > /dev/null

This little script get executed when a user session starts. nmcli is a command line interface to NetworkManager. The first command tells NetworkManager to disable wifi and the second to enable it. In effect this is like unchecking and checking the Enable wifi box in the NetworkManager applet or pushing the hardware switch twice. This force NetworkManager to rescan all available networks including the previously failed auto connect network.

You can see the script in action while starting kde. First the applet shows no connection. Then wifi becomes disabled for a short while and finally if all goes well a connection is established.

13

After the latest NetworkMannager update the quick fix don’t seem to be necessary any more.