i’m using openSUSE 13.2 with Ethernet but i added a wifi card in order to be able to access the web when the ethernet is Ko. I installed 13.2 from the dvd.
How do i activate the wifi access : do i need to turn off the ethernet before ?
I went to yast and set up the wifi device ( Atheros AR9485 , driver ath9k is active) , it seems it’s not completely set though .
In console i used wicked to turn on the wifi device ( # wicked ifup wlp4s0) but i can see that there’s a time out , also it seems it’s unable to translate eap protocol (see below).
What else shall i do ? What’s going wrong ?
Thank you
systemctl -p Id show network.service
Id=wicked.service
# systemctl status network.service
wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (exited) since Tue 2015-01-20 13:38:44 CET; 23min ago
Process: 941 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
Main PID: 941 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/wicked.service
Jan 20 13:38:44 openSUSE132 wicked[941]: device wlp4s0 failed: operation timed out
Jan 20 13:38:44 openSUSE132 wicked[941]: lo up
Jan 20 13:38:44 openSUSE132 wicked[941]: enp3s0 up
Jan 20 13:38:44 openSUSE132 wicked[941]: wlp4s0 setup-in-progress
openSUSE132:~ # systemctl status wickedd.service
wickedd.service - wicked network management service daemon
Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled)
Active: active (running) since Tue 2015-01-20 13:38:14 CET; 25min ago
Main PID: 939 (wickedd)
CGroup: /system.slice/wickedd.service
└─939 /usr/sbin/wickedd --systemd --foreground
Jan 20 13:38:14 openSUSE132 wickedd[939]: unable to translate eap protocol AKA
Jan 20 13:38:14 openSUSE132 wickedd[939]: unable to translate eap protocol AKA'
Jan 20 13:38:14 openSUSE132 wickedd[939]: unable to translate eap protocol FAST
...
I don’t have a good handle on this, since I’m still using openSUSE 13.1 (and prefer using NM anyway), but I did find a bug report which may be of help to you
Some good debug information in comment #2, and comment #3 discusses the use of the nanny daemon for hotplugging (if applicable). Anyway, hopefully you can make some sense of this.
I read it all, thanks for the information.
I’m not sure though if this is a bug linked with wicked or my wifi card.
Shall i add data as in comment 2 or rather like in # 22 ?
Can you confirm that the NetworkManager service is not active at all? I would follow the debug steps that were mentioned in that bug report. Then you will have more useful info to go on.
Here is how to do it:
‒ set DEBUG=all in /etc/sysconfig/network/config
‒ systemctl restart wickedd
‒ wicked --debug all ifup all # systemctl restart wicked
‒ wicked ifstatus all > status.log
‒ wicked show-config > configs.log
‒ journalctl -b -o short-iso > wicked.log
to answer your question : networkmanager was not active, i cheched this following the bug report command lines.
Now this is confusing : shall i use networkmanager or fill a new bug report with wicked ? It seems openSUSE 13.2 introduced wicked too early, it’s brand new and not very well know so far, this making some cases more difficult to solve.
So …as the release notes says that networkmanager can be reactived , i followed the tips there to try this option too, i then rebooted in order to restart all that’s needed (services like wicked, wickedd, wpa_supplicant, network… ) , but then iwconfig still gave me the wifi device not associated. Did i forget something ?
Shall i do something more trying to use networkmanager ?
I then returned to the previous state : reactived wicked and turned off networkmanager using the following :
You choice as to whether you use NM or wicked. (I think NM is easier to configure and connect for those switching wireless networks frequently.)
So …as the release notes says that networkmanager can be reactived , i followed the tips there to try this option too, i then rebooted in order to restart all that’s needed (services like wicked, wickedd, wpa_supplicant, network… ) , but then iwconfig still gave me the wifi device not associated. Did i forget something ?
Shall i do something more trying to use networkmanager ?
Yes, you need to configure a connection using the NM connection editor first.
I then returned to the previous state : reactived wicked and turned off networkmanager using the following :
Okay, so sticking with wicked…
Feb 02 10:07:35 openSUSE132 wpa_supplicant[834]: ioctl[SIOCSIWENCODEEXT]: Invalid argument
Feb 02 10:07:35 openSUSE132 wpa_supplicant[834]: ioctl[SIOCSIWENCODEEXT]: Invalid argument
You might want to share the configuration in /etc/wpa_supplicant/wpa_supplicant.conf, as perhaps there’s an error or mis-configuration there. (Don’t share the passkey of course.)
i agree that NM seems to be easier, known option and easy to use, but i do not know how to use it (yet).
How do you “configure a connection using the NM connection editor” ?
in my opinion wicked is supposed to work (i “hate” it when i need to change defaults) and the futureoption too, so i’d rather have wicked working if possible, but if not i’ll use NM in the meanwhile.
in my opinion wicked is supposed to work (i “hate” it when i need to change defaults) and the futureoption too, so i’d rather have wicked working if possible, but if not i’ll use NM in the meanwhile.
No, both are the current alternatives. The Wicked framework for network configuration and is a replacement for the ifup family of scripts, as explained here. I agree with you though, that it can be frustrating when there is an issue with configuration or similar.
Okay, I have the same as it happens, (but that’s probably just the default install settings). Other references that I’ve seen look more like these examples below
Not sure what else I can advise here, since I’m not familiar with wicked. Is the wireless configuration located in /etc/sysconfig/network/ifcfg… perhaps?
Looking at your ifcfg-wlp4s0 config, I would check that the appropriate authentication protocol for your AP matches what you set here. The config shows PSK (WPA-PSK). Nothing looks wrong with the configuration (assuming authentication details are correct), but you might want to review the settings you made in YaST anyway. The curious error message reported by the wicked daemon was
wickedd[957]: unable to translate eap protocol
but I’m not sure how it applies here, since you appear not to be using EAP. BTW, there is also a WPA-EAP authentication protocol which is supported. You can review the man pages for more info
I did wonder about this parameter though (may or may not be relevant)
WIRELESS_KEY_LENGTH='128
I wonder if this correct or even needs to be used here for WPA-PSK. (I doubt it.)
I note that it is mentioned
WIRELESS_KEY_LENGTH
Defines the length in bits for all keys used. There are currently 40 and 104
bit keys supported. Sometimes they are also called 64 resp. 128 bits
(depends on whether you count the 24 bit initialization vetor or not).
This variable is only meaningful if you enter the key as passphrase.
WIRELESS_WPA_PSK
When using WPA-PSK authentication, you need to specify your preshared key
here. The key is used for authentication and encryption purposes. You can
enter it in hex digits (needs to be exactly 64 digits long) or as passphrase
getting hashed (8 to 63 ASCII characters long).
i don’t get the following : what is resp. ? what does it mean ?
"Sometimes they are also called 64 resp. 128 bits
(depends on whether you count the 24 bit initialization vetor or not)".
in WIRELESS_WPA_PSK : i entered a passphrase myself , i understand that this passphrase is going to be hashed by the system after . Is this correct ?
( as passphrase getting hashed (8 to 63 ASCII characters long). )
Also i added in the interface conf file
# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
###ajouts pour la configuration du wifi, au départ le fichier n'a que les 2 1eres lignes ce qui n'est pas complet.
### the following i added for file was not complete as default
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="xx"
proto=WPA RSN
key_mgmt=WPA-PSK WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
psk=yyyyyyyy
}
and then rebooted but i still have no association :
# iwconfig
wlp4s0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
enp3s0 no wireless extensions.
lo no wireless extensions.
openSUSE132:~ # ifup wlp4s0
wicked: device wlp4s0 failed: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
wlp4s0 setup-in-progress
Can you try removing that entry, or perhaps commenting it out?
in WIRELESS_WPA_PSK : i entered a passphrase myself , i understand that this passphrase is going to be hashed by the system after . Is this correct ?
( as passphrase getting hashed (8 to 63 ASCII characters long). )
Yes, that’s correct.
As far as wicked is concerned, I don’t think it uses wpa_supplicant.conf (although wpa_supplicant daemon is used itself of course), so this won’t help. It is used by distros using systemd-networkd, or those using CLI to connect, (but openSUSE does not yet). I include the following pages only for interest’s sake:
