4 ms·

> but only on Linux Are you using wpa_supplicant 2.9? Do not update to 2.10! I had the same experience with 2.9, but with 2.10, I cannot connect at all, not e

> but only on Linux Are you using wpa_supplicant 2.9? Do not update to 2.10! I had the same experience with 2.9, but with 2.10, I cannot connect at all, not even with WPA2 (with WPA2+3 Transitional on the AP). Downgraded back to 2.9 and it works again.

andix 4y ago
No idea. I use Ubuntu. And it just works. That’s what I want, and I prefer not to know more ;)
- deepsun 4y ago
  Good for you, but on this site curiosity is explicitly encouraged.
  - gjs278 4y ago
glowingly 4y ago
I bypassed WPA supplicant on Tumbleweed, and manually setup the connection. I did think it was rather odd that my WiFi AP stopped allowing my linux laptop to connect, even though it worked right before I moved from Fedora -> Tumbleweed. But even a new Fedora live ISO (I guess all Fedora ISOs are live by default) was unable to connect. Eventually figured it was the current version of WPA Supplicant at fault, not the WiFi AP, and not the HW in my laptop. But it is somewhat annoying when something that worked just an hour ago, flatly doesn't.
pantalaimon 4y ago
Does it work with iwd?
- vetinari 4y ago
  Yes, but WPA2-only, just like Windows.
exikyut 4y ago
1. Why?! (Yelled in wpa_supplicant's general direction, not yours) 2. What error messages were you seeing in wpa_cli, out of curiosity?
- vetinari 4y ago
  https://bugzilla.opensuse.org/show_bug.cgi?id=1195395 https://bugzilla.opensuse.org/show_bug.cgi?id=1195395 https://bugzilla.redhat.com/show_bug.cgi?id=2050840 https://bugzilla.redhat.com/show_bug.cgi?id=2050840 Reading through the opensuse bugzilla I tried again, and it works! NetworkManager 1.38+ needed. It is interesting, that the fix is in NetworkManager (https://bugzilla.opensuse.org/show_bug.cgi?id=1195395#c47 https://bugzilla.opensuse.org/show_bug.cgi?id=1195395#c47).
jlarocco 4y ago
Interesting. I had the hardest time getting wpa_supplicant working on a new Debian install last weekend, and eventually gave up and switched to iwd, which was new to me, but worked immediately Checking now, I have wpa_supplicant 2.10, so I wonder how much of my problem was due to that. iwd's been great so far - I'm no expert so maybe there are technical advantages, but I don't see any reason to go back to wpa_supplicant.

andix 4y ago

No idea. I use Ubuntu. And it just works. That’s what I want, and I prefer not to know more ;)

deepsun 4y ago
Good for you, but on this site curiosity is explicitly encouraged.
- gjs278 4y ago

glowingly 4y ago

I bypassed WPA supplicant on Tumbleweed, and manually setup the connection. I did think it was rather odd that my WiFi AP stopped allowing my linux laptop to connect, even though it worked right before I moved from Fedora -> Tumbleweed. But even a new Fedora live ISO (I guess all Fedora ISOs are live by default) was unable to connect. Eventually figured it was the current version of WPA Supplicant at fault, not the WiFi AP, and not the HW in my laptop. But it is somewhat annoying when something that worked just an hour ago, flatly doesn't.

pantalaimon 4y ago

Does it work with iwd?

vetinari 4y ago
Yes, but WPA2-only, just like Windows.

exikyut 4y ago

1. Why?! (Yelled in wpa_supplicant's general direction, not yours) 2. What error messages were you seeing in wpa_cli, out of curiosity?

vetinari 4y ago
https://bugzilla.opensuse.org/show_bug.cgi?id=1195395 https://bugzilla.opensuse.org/show_bug.cgi?id=1195395 https://bugzilla.redhat.com/show_bug.cgi?id=2050840 https://bugzilla.redhat.com/show_bug.cgi?id=2050840 Reading through the opensuse bugzilla I tried again, and it works! NetworkManager 1.38+ needed. It is interesting, that the fix is in NetworkManager (https://bugzilla.opensuse.org/show_bug.cgi?id=1195395#c47 https://bugzilla.opensuse.org/show_bug.cgi?id=1195395#c47).

jlarocco 4y ago

Interesting. I had the hardest time getting wpa_supplicant working on a new Debian install last weekend, and eventually gave up and switched to iwd, which was new to me, but worked immediately Checking now, I have wpa_supplicant 2.10, so I wonder how much of my problem was due to that. iwd's been great so far - I'm no expert so maybe there are technical advantages, but I don't see any reason to go back to wpa_supplicant.