[opensuse-arm] Wi-Fi connections on Raspberry Pi 1 B
Hi all, I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails. Using "iwlist wlan0 scan" the only obvious difference is that one reports to use CCMP, the one which succeeds, and the other uses TKIP, which does not succeed. In the information I found on the Internet I see that the configuration for wpa_supplicant may contain information about the support/use of these protocols. However the file /etc/wpa_supplicant/wpa_supplicant.conf does not contain this information, but the process wpa_supplicant has been started with the -u option, which enables a DBus control interface. So I assume that this kind of information will be supplied by wicked. However I can't find if TKIP is supported in openSUSE 13.2 for the the Raspberry Pi. Any information? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf <f.de.kruijf@gmail.com>:
Hi all,
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
Using "iwlist wlan0 scan" the only obvious difference is that one reports to use CCMP, the one which succeeds, and the other uses TKIP, which does not succeed.
In the information I found on the Internet I see that the configuration for wpa_supplicant may contain information about the support/use of these protocols. However the file /etc/wpa_supplicant/wpa_supplicant.conf does not contain this information, but the process wpa_supplicant has been started with the -u option, which enables a DBus control interface. So I assume that this kind of information will be supplied by wicked. However I can't find if TKIP is supported in openSUSE 13.2 for the the Raspberry Pi.
Any information?
I don't think any of that code is RPi/Arm specific. I assume your Wifi dongle is USB based. If so, have you tried to attach it to an x86 system with 13.2 to narrow it down? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber:
Hi,
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured.
What do you mean by RTC? And NTP means Network Tine Protocol? What I am really looking for are means to get more debug output than "ifup wlan0 -o debug" delivers. So I can see what goes wrong. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 26.02.2015 um 10:12 schrieb Freek de Kruijf:
Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber:
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured.
What do you mean by RTC?
Real time clock, i.e. `date`.
And NTP means Network Tine Protocol?
Yes. Can be configured through the yast time(zone) settings. Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op donderdag 26 februari 2015 10:44:17 schreef Andreas Färber:
Am 26.02.2015 um 10:12 schrieb Freek de Kruijf:
Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber:
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured.
What do you mean by RTC?
Real time clock, i.e. `date`.
And NTP means Network Tine Protocol?
Yes. Can be configured through the yast time(zone) settings.
Andreas
I have a test set up with the RPi connected via the UTP port and two different Wi-Fi USB dongles in the two USB ports of the RPi. The clock is synchronized using NTP via the wired connection. So there is nothing wrong with the RTC and NTP. The two Wi-Fi interfaces are configured the same way apart from the SSID and IP address. I exchanged the SSIDs of these interfaces and both connect to one AP and not to the other AP. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/26/2015 05:47 AM, Freek de Kruijf wrote:
Op donderdag 26 februari 2015 10:44:17 schreef Andreas Färber:
Am 26.02.2015 um 10:12 schrieb Freek de Kruijf:
Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber:
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured.
What do you mean by RTC?
Real time clock, i.e. `date`.
And NTP means Network Tine Protocol?
Yes. Can be configured through the yast time(zone) settings.
Andreas
I have a test set up with the RPi connected via the UTP port and two different Wi-Fi USB dongles in the two USB ports of the RPi. The clock is synchronized using NTP via the wired connection. So there is nothing wrong with the RTC and NTP. The two Wi-Fi interfaces are configured the same way apart from the SSID and IP address. I exchanged the SSIDs of these interfaces and both connect to one AP and not to the other AP.
I see a number of red herrings in this thread. The first is that time has anything to do with it. I also doubt that this has anything to do with RPi or ARM. The two AP's are *not* configured the same. In your first E-mail, you said that one uses TKIP and the other uses CCMP. That usually means WPA for the TKIP case, and WPA2 for CCMP or AES. Please supply the output of 'ps ax | grep wpa_supplicant'. Also, please supply the output of 'sudo /usr/sbin/iwlist scan' or 'sudo iw wlan0 scan'. If the device has a name other than wlan0, adjust the second command accordingly. It would be helpful if you identified the wireless device and driver. I have no experience with wicked, but I suspect it is the problem. To my knowledge, all wifi drivers handle both WPA and WPA2 encryption correctly. Larry -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 26.02.2015 um 17:37 schrieb Larry Finger:
On 02/26/2015 05:47 AM, Freek de Kruijf wrote:
Op donderdag 26 februari 2015 10:44:17 schreef Andreas Färber:
Am 26.02.2015 um 10:12 schrieb Freek de Kruijf:
Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber:
Am 25.02.2015 um 22:11 schrieb Freek de Kruijf:
I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails.
In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured.
What do you mean by RTC?
Real time clock, i.e. `date`.
And NTP means Network Tine Protocol?
Yes. Can be configured through the yast time(zone) settings.
Andreas
I have a test set up with the RPi connected via the UTP port and two different Wi-Fi USB dongles in the two USB ports of the RPi. The clock is synchronized using NTP via the wired connection. So there is nothing wrong with the RTC and NTP. The two Wi-Fi interfaces are configured the same way apart from the SSID and IP address. I exchanged the SSIDs of these interfaces and both connect to one AP and not to the other AP.
I see a number of red herrings in this thread. The first is that time has anything to do with it.
I can assure you that connecting to the SUSE Wifi (WPA2 Enterprise?) does not work when the clock is significantly off. I've seen that on both my AC100's internal Wifi and on my Chromebook with a Wifi dongle. Both use NetworkManager. At home with WPA2 Personal (?) it works without problems, independent of the clock.
I also doubt that this has anything to do with RPi or ARM.
Yep. However, ARM boards differ from a PC in often not having a battery-backed RTC and thus causing certain known issues, so that it's not entirely wrong to ask on the -arm list. When sufficient info is known about the non-working setup, a Bugzilla entry might be better though. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Färber wrote:
I can assure you that connecting to the SUSE Wifi (WPA2 Enterprise?) does not work when the clock is significantly off. I've seen that on both my AC100's internal Wifi and on my Chromebook with a Wifi dongle. Both use NetworkManager.
This depends very much on how your WPA2 Enterprise setup is. Some examples where time sync is more or less important: - validity period of EAP/TLS certs - Kerberos authentication
At home with WPA2 Personal (?) it works without problems, independent of the clock.
WPA2 Personal is pretty simple.
I also doubt that this has anything to do with RPi or ARM.
Yep. However, ARM boards differ from a PC in often not having a battery-backed RTC and thus causing certain known issues, so that it's not entirely wrong to ask on the -arm list. When sufficient info is known about the non-working setup, a Bugzilla entry might be better though.
I have WLAN troubles with wickedd setup on several non-ARM platforms where NetworkManager simply works: - openSUSE 13.2 x86_64 (1. notebook) - openSUSE Factory x86_64 (2. notebook) I'm running openSUSE Factory_ARM on rasperry pi (with a USB WLAN adapter) just fine with hostapd. Not tried it as normal WLAN client with wickedd yet. Ciao, Michael.
participants (6)
-
Alexander Graf -
Andreas Färber -
Freek de Kruijf -
Freek de Kruijf -
Larry Finger -
Michael Ströder