Re: NM+WPA_Supplicant+Systemd trouble: can't connect to WLAN
- From: Pavel Simerda <psimerda redhat com>
- To: Nickolai Dobrynin <ndobrynin gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: NM+WPA_Supplicant+Systemd trouble: can't connect to WLAN
- Date: Tue, 9 Sep 2014 05:41:13 -0400 (EDT)
See https://bugzilla.gnome.org/show_bug.cgi?id=736206#c5
----- Original Message -----
From: "Nickolai Dobrynin" <ndobrynin gmail com>
To: mje posix co za
Cc: networkmanager-list gnome org
Sent: Saturday, September 6, 2014 8:15:59 PM
Subject: Re: NM+WPA_Supplicant+Systemd trouble: can't connect to WLAN
Thanks Mark -
1. I don't see how daemons could be starting in
a wrong order, in my particular case. WPA Supp is not
started except by NM. NM spawns its own instance of WPA
Supp, and it's the only instance of it I have. Am I
missing something? Should there be another one, e.g.,
wpa_supplicant wlp3s0? But what purpose would it serve?
2. Should I maybe upgrade or downgrade some of these
packages? I currently run
WPA Supplicant - v. 2.0-r2
NetworkManager - v. 0.9.8.10-r1
Systemd - v. 215-r3
Kernel - v. 3.14.14
Many thanks again.
PS I may also go Mate or XFCE if I can't get this working.
I just can't fathom why the Supp would work great with DHCPCD
but not with NM *under the exact same configuration*. I
cannot wrap my brain around this. I hope someone with deep
knowledge of NM speaks up.
_______________________________________________
networkmanager-list mailing list
networkmanager-list gnome org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]