Am 05.07.2013 09:19, schrieb Roland Mas: > Michael Biebl, 2013-07-04 22:57:16 +0200 : > >> Hi Roland, >> >>> Jul 4 16:02:25 elastomir wpa_supplicant[1700]: nl80211: 'nl80211' generic >>> netlink not found >>> Jul 4 16:02:25 elastomir wpa_supplicant[1700]: Failed to initialize driver >>> 'nl80211' >>> Jul 4 16:02:25 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWENCODEEXT]: >>> Invalid argument >>> Jul 4 16:02:25 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWENCODEEXT]: >>> Invalid argument >>> Jul 4 16:02:31 elastomir wpa_supplicant[1700]: eth1: Trying to >>> associate with 14:0c:76:f9:23:bd (SSID='FreeWifi' freq=2472 MHz) >>> Jul 4 16:02:31 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWGENIE]: >>> Operation not supported >>> Jul 4 16:02:31 elastomir wpa_supplicant[1700]: eth1: Association >>> request to the driver failed >> >> >> That looks suspcious. Do you get a reliable network connection if you >> use ifupdown+wpa_supplicant directly? > > I don't really know. Since the wireless network I'm trying to attach > to is unencrypted, I do without wpa_supplicant. But ifupdown+iwconfig > do lead to a reliable connection, yes.
That is hitting completely different code paths, so that the result differs is not too unexpected. Is it possible you can try to setup wpa_supplicant to use both wext and nl80211 and report back with the results. This should help to narrow down where the problem is. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
