After upgrading from OpenSuse 41.2 to v42.3, I encountered some problems and the latest of them is the loss of wireless communication. The computer is only connected via this wifi dongle.
I had it running, until I performed the latest updates. After updates, the Wifi didn’t work and I could not configure it. I used to configure it through Yast Network Settings (Wicked Service).
I use a USB wifi dongle, RTL8191SU (the name recognised by OpenSuse is the same as in Windows).
Now I downgraded to OpenSuse 42.1 and I am still not able to use the network. The results presented below are the same for OpenSuse 42.3.
dmesg | less shows:
New USB device found, idVendor=0bda, idProduct=8172
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: RTL8191S WLAN Adapter
Manufacturer: Realtek
SerialNumber: 00e04c000001
iwconfig:
wlan0 - unassociated Nickname: “rtl_wifi”
Mode: Managed Access Point: Not-Associated Sensitivity: 0/0
Retry: off RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality: 0 Signal Level: 0 Noise Level: 0
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0
iwlist scan
wlan0 Scan completed:
… Cell 08 Address: E8:DE:27:89:0d:88 (I changed some values)
ESSID: MyNetwork
Protocol: 802.11bgn
Mode: Master
Frequency: 2.462 GHz (channel 11)
Encryption key: on
Bit rates: many
Extra: wpa_ie=dd1a00…
IE: WPA Version 1
Group Cipher: TKIP
Extra: rsn_ie=30180…
IE: WPA Version 1
…
Signal Level: 76/100
Under Hardware Information, it shows Kernel Driver: 8712u
I am able to ping the static IP I assigned to the Wifi dongle (192.168.1.12) but I can’t ping the router and DNS (192.168.1.1). It gives error Destination Host Unreachable
I’ve seen many people indicating their wlan0 is unassociated, and I suspect the problem is related to this. I tried all kind of command line commands, such as “ifconfig wlan0 up”, “iwconfig wlan0 txpower auto”, etc
ifdown wlan0;ifup wlan0
wlan0 device-ready
wlan0 up
In second terminal, I can see one type of warnings. All the other messages are just info. Because I am typing the messages from keyboard on another computer, I won’t display all of them.
In second terminal, I can see one type of warnings. All the other messages are just info. Because I am typing the messages from keyboard on another computer, I won’t display all of them.
Thanks. At some stage I wanted to try using NetworkManager and I probably had both wicked and NetworkManager running at the same time.
I stopped and disabled NetworkManager.
Now, I get:
systemctl status NetworkManager
NetworkManager,service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager, service; disabled)
Active: inactive (dead)
systemctl status wicked
wicked, service - wicked managed network interface
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (Exited)
Process: 966 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0,SUCCESS)
Main PID: 966 (code: exited, status=0;SUCCESS)
CGroup: /system/slice/wicked.service
wicked[966]: lo up
wicked[966]: wlan0 up
iwconfig
em1 - no wireless extensions
lo - no wireless extentions
wlan0 - unassociated Nickname: "rtl_wifi"
Mode: managed Access Point: Not-Associated Sensitivity:0/0
When I ping the IP assigned to wlan0, it responds. But for the gateway, it reports network unreachable.
I moved the computer to another room, where I have the router and I configured the ethernet board. I am running the updates now, hopefully after this step, I will be able to get the wireless running.
Good. FWIW, I prefer NM as I’m using a laptop that moves between lots of different network environments, so I have several network connection profiles to choose from.
When I ping the IP assigned to wlan0, it responds.
That’s irrelevant as you’ve assigned a static IP address to this network interface, so you’ll be able to ping it regardless of the wifi connection status.
I moved the computer to another room, where I have the router and I configured the ethernet board. I am running the updates now, hopefully after this step, I will be able to get the wireless running.
Not sure about that, but report back when you’re done.
Thanks for ideas. I’ve been working to fix this issue since last week. I’ve redone all the settings from scratch, with upgrades and installations of the OS many times. The fact I can post this message from the cabled connection means the DNS is working fine. I am not even able to ping my router from the wireless connection, and the DNS has nothing to do with that.
The USB Wireless dongle is not defective, because I can use it when I boot the computer in Windows.
My router is configured to use encryption, all other computers work fine with this setting, even OpenSuse worked fine for years with the same settings, so there is no need to change to unencrypted.
Because I can see iwlist, I know the hardware works fine (I have another USB dongle, different model, which I tried, hoping it will use a different driver, but it looks like Linux is not automatically recognizing the new device, I could not see any difference and still could not connect).
The IP address ending with 12 is one of the tens of different random IP Addresses I allocated. I only have two other computers running, so the chance of collision is very small anyway and if those computers stop working I will know the IP is chosen incorrectly.
I’ve completed the OpenSuse 42.1 updates, the system is up-to-date now, it just still does the same as before with wireless.
Please run the commands in posts #7 and #8. If possible, use wired internet to gain internet connectivity and post the output. (Enclose within code tags, refer to the ‘#’ button in the forum editor.) Alternatively, copy/paste the output to a text file, transfer to a memory stick and post via an internet-connected machine.
I am reading from forums, and there is a mention of the file wpa_supplicant.conf.
I found two such files on my system. One is located in folder /wpa/wpa_supplicant and this is what it contains:
I made a big progress and the irony is that I am not yet sure what caused it. It could be that I changed the content of the file wpa_supplicant.conf.
Now, when I run the command iwconfig, I get:
linux-21ul:~ # iwconfig
em1 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"T24" Nickname:"rtl_wifi"
Mode:Managed Frequency:2.437 GHz Access Point: E8:DE:27:89:0D:87
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=100/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
So, unexpectedly, the wlan0 interface became associated. I am still unable to ping my router, but it is a big progress. I hope to find how it got fixed!
This is the content of the wpa_supplicant.conf file, after I used a sample file to modify it.
After checking again the content of the wpa_supplicant.conf and comparing the content with the description from iwlist, I found the group was not matching the description, so I edited it. The editor of choice for me is Kate, but I have to start it from Super User Terminal.
This post is sent using the wireless dongle.
Thanks to everybody who contributed, especially to deano_ferrari - you put me on the right track.
Content of /etc/wpa_supplicant/wpa_supplicant.conf file:
ctrl_interface=/var/run/wpa-supplicant
ap_scan=1
network={
ssid="T24"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=TKIP (changed from previous entry, based on the information about group cipher using the command "iwlist wlan0 scanning")
psk="Password in clear"
}
I wanted to know what happens if I restore the content of the original /etc/wpa_supplicant/wpa_supplicant.conf file and I put back the original content. It works this way as well.
However, I suspect it may still have had an effect when I first changed it.
I thought I will look through the terminal commands I issued during my struggle. I could see the list using the command “cat ~/.bash_history”. It is a very long list.
I saved the list to a text file and I will go through it only in case there will be future problems.