Can someone Please Help Me???. I admit that I am not network literate!! I am truly frustrated with my lack of wireless connection in Leap 42.2. I have been bouncing back and forth from Wicked to Network Manager with seemingly no consistent connection. It seems like every time I turn OpenSuse on something changes. I decided to go back to Wicked with my RTL8187 and nothing I do makes a connection. I am running KDE. Can anyone tell me where to start to get this wireless running on Wicked? Since I have no connection in Linux (I am on my Windows machine now and Windows handles everything the way it is suppose to) I will have to report output manually. Thanks to anyone who can help me make sense of all of this!
Am Mon, 26 Jun 2017 15:26:01 GMT
schrieb jdcart15 <jdcart15@no-mx.forums.microfocus.com>:
> Since I have no connection in Linux (I am on my
> Windows machine now and Windows handles everything the way it is suppose
> to) I will have to report output manually
Nope, you can always redirect the output of a command to a file by using
command >> outputfile
and transfer the output file to some medium which can be read by windows (USB
stick or your windows partition if you are running a dual boot system.)
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
I have my rtl8187 usb working on Networkmanager. I can output any command from this machine if someone can help me diagnose why Wicked will not configure it. I would like to know the answer to this before I proceed with a newly purchased more up to date adapter. Anyone???
Do you have a working configuration for it? If not, configure via…
YaST > System > Network Settings > Overview, slect the wireless device, and ‘Edit’ to configure… click ‘Ok’ when done.
If you believe you have configured the device, then show us the configuration (eg wlan0)…
cat /etc/sysconfig/network/ifcfg-wlan0
Thank you Ferrari man for offering to help me. I tried the Yast routine that you have mentioned 100 times to no avail. Adapter stays dead no matter what, unless I am not entering the values that I should be entering. Maybe you can help me with that? Anyway, here is the output you requested.
**linux-fxo6:~ #** cat /etc/sysconfig/network/ifcfg-wlan0
BOOTPROTO='dhcp'
BROADCAST=''
DHCLIENT_SET_DEFAULT_ROUTE='yes'
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='RTL8187 Wireless Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='Jacksonman'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='h:qinq9vfg0myk'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='no'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
I was having stability problems with networkmanager although it seems to be improved now. But that is why I wanted to try Wicked to see if I could get added stability. i.e. losing my connection out of nowhere. Networkmanager has always connected me. Wicked never has yet. Why?
Are you sure you have the authentication mode configured correctly? Your configuration suggests WEP Open. (If so, that’s not very secure.)
WIRELESS_AUTH_MODE='open'
I’m using WPA-PSK, and I would expect most wifi user’s would be connecting to APs using similar authentication/encryption protocols.
I was having stability problems with networkmanager although it seems to be improved now. But that is why I wanted to try Wicked to see if I could get added stability. i.e. losing my connection out of nowhere. Networkmanager has always connected me. Wicked never has yet. Why?
Connection stability is unlikely to be affected by which connection manager you’re using. That’s a different issue, and can be due to interference, weak RSSI, and sometimes power management issues can have a detrimental effect.
Thanks for noticing the encryption problem. I have no idea how that happened. It prompted me for the password. How do I correct this problem? This is crazy. I deleted the connection and rebooted but it came back up non-encrypted even though it asked for the password.
I changed the password and it immediately kicked me off and asked for a password. I put in the new password, got reconnected and got the following result. . .What the heck is happening?
**linux-fxo6:~ #** /usr/sbin/iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"Jacksonman"
Mode:Managed Frequency:2.412 GHz Access Point: 6A:A1:95:6F:84:8C
Bit Rate=48 Mb/s Tx-Power=30 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-24 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:176 Invalid misc:4 Missed beacon:0
eth0 no wireless extensions.
Just to be clear - my last post was specifically about the configuration that applies to wicked. Is that what you’re now using?
Well that output shows that you’re connected… where did you change the password? Remember , where not watching over your shoulder, so you need to be a little more descriptive. Are you now using NM or wicked?
Here is the answer.
**linux-fxo6:~ #** iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 6A:A1:95:6F:84:8C
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=70/70 Signal level=-30 dBm
Encryption key:on
ESSID:"Jacksonman"
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=000000005d292122
Extra: Last beacon: 164ms ago
IE: Unknown: 000A4A61636B736F6E6D616E
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 0706555320010D1E
IE: Unknown: 200100
IE: Unknown: 23021100
IE: Unknown: 2A0100
IE: Unknown: 32040C121860
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2D1A2D0017FFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601001300000000000000000000000000000000000000
IE: Unknown: 7F080400000000000040
IE: Unknown: DD0A0017F206010103010000
IE: Unknown: DD0D0017F20602010648A1956F848D
IE: Unknown: DD090010180201001C0000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
Cell 02 - Address: E8:33:81:25:4B:30
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=35/70 Signal level=-75 dBm
Encryption key:on
ESSID:"ATT2s3V8J3"
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=00000313022cc820
Extra: Last beacon: 2292ms ago
IE: Unknown: 000A41545432733356384A33
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1AFC191FFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1606080400000000000000000000000000000000000000
IE: Unknown: DD090010180204F02C0000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
What answer? You’ve lost me 
I do not have the ability to connect with wicked. I can only use NM. This is what I need help with!! I think that every one is just as stumped as I am. Any possibility of getting the wicked team from Suse involved in this problem? Thanks for trying to help! Answer to encryption problem
Am Thu, 29 Jun 2017 11:16:01 GMT
schrieb jdcart15 <jdcart15@no-mx.forums.microfocus.com>:
> Any possibility of getting the wicked team from Suse
> involved in this problem?
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Why wicked if it works with Networkmanager?
For Wlan the easier way to get Internet…
Well back at post #6 that’s what I was trying to do, and specifically not authenticating correctly is one reason that can prevent a working wireless association. I still don’t know what the information in post #8 was trying to prove!
I think that every one is just as stumped as I am.
You haven’t provided the necessary info yet! You need to work methodically with us. This will involve answering questions and running commands to capture output.
Switch to using wicked again (I assume you know how to do that), and reboot. Once up and running examine the journal log for wicked-related messages…
sudo journalctl -u wicked
or
sudo journalctl -b |grep wicked
I have purchased a new wireless adapter (RTL8812au) and have it working on network manager. Its performance is much superior to the RTL8187. Thanks to AK for packaging the driver and Sauerland for helping me install the driver.
I guess the fact that I cannot configure it in Wicked does not matter, except the fact that it bugs me that things are not as they should be. Anyway, I have put the output that Ferrari man requested into a text doc and it is posted here.
**linux-fxo6:~#**sudo journalctl -u wicked
-- Logs begin at Thu2017-06-08 19:20:54 EDT, end at Fri 2017-06-30 11:13:20 EDT. --
Jun08 19:21:01 linux-fxo6 systemd[1]: Starting wicked managed networkinterfaces...
Jun 08 19:21:18 linux-fxo6 wicked[1061]: lo up
Jun 08 19:21:18 linux-fxo6 wicked[1061]: eth0 up
Jun 08 19:21:18 linux-fxo6 systemd[1]: Started wicked managednetwork interfaces.
Jun 08 19:29:25 linux-fxo6 systemd[1]:Reloading wicked managed network interfaces.
Jun 08 19:29:55linux-fxo6 wicked[6709]: wlan0 setup-in-progress
Jun 08 19:29:55 linux-fxo6 systemd[1]: Reloaded wicked managednetwork interfaces.
Jun 08 19:33:31 linux-fxo6 systemd[1]:Stopping wicked managed network interfaces...
Jun 08 19:33:32linux-fxo6 wicked[8520]: eth0 device-ready
Jun 08 19:33:32 linux-fxo6 wicked[8520]: wlan0 device-ready
Jun 08 19:33:32 linux-fxo6 systemd[1]: Stopped wicked managednetwork interfaces.
**--Reboot --**
Jun 08 19:34:24 linux-fxo6 systemd[1]: Startingwicked managed network interfaces...
Jun 08 19:34:54 linux-fxo6wicked[1059]: lo up
Jun 08 19:34:54 linux-fxo6 wicked[1059]: eth0 up
Jun 08 19:34:54 linux-fxo6 wicked[1059]: wlan0 setup-in-progress
Jun 08 19:34:54 linux-fxo6 systemd[1]: Started wicked managednetwork interfaces.
Jun 08 19:42:17 linux-fxo6 systemd[1]:Reloading wicked managed network interfaces.
Jun 08 19:42:48linux-fxo6 wicked[3873]: wlan0 device-ready
Jun 08 19:42:48 linux-fxo6 wicked[3873]: wlan0 setup-in-progress
Jun 08 19:42:48 linux-fxo6 systemd[1]: Reloaded wicked managednetwork interfaces.
Jun 08 19:43:11 linux-fxo6 systemd[1]:Stopping wicked managed network interfaces...
lines1-23
I will gladly continue to work with anyone who wants to get to the end of this. However I did report it as a bug and discovered that the bug has been previously reported with an Intel adapter. It appears that there is no priority to solve the problem. Thanks to everyone who responded to my thread.
I have to admit that I am a happy camper with this new stick. So far it is performing very well and I will stay with my desktop setup. I know that in the future, wireless connections will become more and more important.
Am Fri, 30 Jun 2017 15:36:02 GMT
schrieb jdcart15 <jdcart15@no-mx.forums.microfocus.com>:
>t appears that there is no priority to solve the problem.
Surprise, Surprise …
As said before, screw wicked and use NWM, I gave up on wicked after reporting
a slightly similar and IMHO even worse bug and got no response at all.
https://bugzilla.opensuse.org/show_bug.cgi?id=979160
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Thanks AK for packaging the RTL8812au. Great job. It’s like I have a new computer with this stick. It is a performer!! I am in love with my Opensuse computer again!