Configure certs/keys/passwords in wpa_supplicant.conf, do "initctl stop network-manager", then run wpa_supplicant manually and everything works like a charm. Run network-manager, the applet or nm-connection-editor won't let me configure the connection, and additionally get in the way of wpa_supplicant.
It appears that newer network-manager-applet and NetworkManager checkouts from Git as of at least 2009-10-20 might fix this problem (or cherry-picking fixes if needed), as there are pertinent log entries, for instance:
nm-applet:
commit 39bf65351dd8d8dc6a5740ff0644999efddad049
Author: Dan Williams <email address hidden>
Date: Mon Oct 19 12:27:23 2009 -0700
applet: request secrets in the applet's wireless dialog
Somewhat broken by the libnm-glib settings service refactor,
but it wouldn't have worked with system connections before anyway,
since nothing explicitly requested system setting secrets from
the wireless dialog. (The connection editor was OK)
This commit basically refactors the population of the various
GtkEntry widgets for secrets and the TLS private key filepicker to
happen both at UI creation time, *and* to update them after
getting secrets. The wireless dialog now explicitly requests
secrets from a connection every time that connection is selected
from the Connection: combo, and when the secrets come back populates
the UI with them, which triggers dialog validation, which will
then enable the Connect... button.
nm:
commit 40c91efa212219658932f36a3fb9c63ecc14aad3
Author: Dan Williams <email address hidden>
Date: Sun Oct 18 23:36:47 2009 -0700
libnm-util: fix checking for TLS and TTLS phase2 secrets
Two errors here; first, need_secrets_tls() was not updated correctly
for the certificate paths changes that landed recently, and would
have incorrectly returned "no secrets required" for the PATH scheme.
Second, an incorrect strcmp() comparison in need_secrets_phase2()
meant that the wrong TTLS phase2 method would get asked if it
required secrets.
I can confirm the original report.
Configure certs/keys/ passwords in wpa_supplicant. conf, do "initctl stop network-manager", then run wpa_supplicant manually and everything works like a charm. Run network-manager, the applet or nm-connection- editor won't let me configure the connection, and additionally get in the way of wpa_supplicant.
It appears that newer network- manager- applet and NetworkManager checkouts from Git as of at least 2009-10-20 might fix this problem (or cherry-picking fixes if needed), as there are pertinent log entries, for instance:
nm-applet:
commit 39bf65351dd8d8d c6a5740ff064499 9efddad049
Author: Dan Williams <email address hidden>
Date: Mon Oct 19 12:27:23 2009 -0700
applet: request secrets in the applet's wireless dialog
Somewhat broken by the libnm-glib settings service refactor,
but it wouldn't have worked with system connections before anyway,
since nothing explicitly requested system setting secrets from
the wireless dialog. (The connection editor was OK)
This commit basically refactors the population of the various
GtkEntry widgets for secrets and the TLS private key filepicker to
happen both at UI creation time, *and* to update them after
getting secrets. The wireless dialog now explicitly requests
secrets from a connection every time that connection is selected
from the Connection: combo, and when the secrets come back populates
the UI with them, which triggers dialog validation, which will
then enable the Connect... button.
nm: 58932f36a3fb9c6 3ecc14aad3
commit 40c91efa2122196
Author: Dan Williams <email address hidden>
Date: Sun Oct 18 23:36:47 2009 -0700
libnm-util: fix checking for TLS and TTLS phase2 secrets
Two errors here; first, need_secrets_tls() was not updated correctly
for the certificate paths changes that landed recently, and would
have incorrectly returned "no secrets required" for the PATH scheme.
Second, an incorrect strcmp() comparison in need_secrets_ phase2( )
meant that the wrong TTLS phase2 method would get asked if it
required secrets.