http://bugzilla.suse.com/show_bug.cgi?id=916042
--- Comment #3 from Pawel Wieczorkiewicz
Hi ;)
i don't know if i'm using wpa 1 or 2, where can i see that ?
i provided a .tgz file attached , is it not ok ? this may help :
# cd /home/fabrice/debug/ openSUSE132:/home/fabrice/debug # ls wicked-bug-report-data.tgz wicked-config.log wicked-status.log wicked.log wpa_supplicant.log openSUSE132:/home/fabrice/debug # cat wpa_supplicant.log Successfully initialized wpa_supplicant wlp4s0: CTRL-EVENT-TERMINATING 1422885313.178740: wpa_supplicant v2.2 1422885313.178764: random: Trying to read entropy from /dev/random 1422885313.179202: dbus: Register D-Bus object '/fi/w1/wpa_supplicant1' 1422885313.179380: Providing DBus service 'fi.w1.wpa_supplicant1'. 1422885313.179590: Providing DBus service 'fi.epitest.hostap.WPASupplicant'. 1422885313.179599: Successfully initialized wpa_supplicant 1422885313.179609: random: Got 20/20 bytes from /dev/random
Thanks ;)
Yes, it is not enough, because wpa_supplicant has not been started in debugging mode, thus we do not have enough logs to analyze the issue. Please restart your wpa_supplicant in the debugging mode (By adding -dddt parameter, how to do it is described here: https://bugzilla.suse.com/show_bug.cgi?id=902771#c2. Then please try to connect to your wireless network again and once again collect logs and attach it here, best with the procedure described here: https://en.opensuse.org/openSUSE:Bugreport_wicked. Regarding the WPA1 vs WPA2 you should check with your wireless network AP which settings has been used. Alternatively you could you the following procedure: 1) ifup $YOUR_WIRELESS_INTERFACE It does not matter if it failed or not, at least it should be up. 2) iwlist $YOUR_WIRELESS_INTERFACE scanning essid $YOUR_SSID And provide the output from the last command to us. -- You are receiving this mail because: You are on the CC list for the bug.