Description of problem: I would like to connect to a wlan which is secured with IEEE8021X but the connect button of the network manager dialog seems to be disabled. Version-Release number of selected component (if applicable): How reproducible: Manually add a new wireless network with IEEE8021X security. Fill in a username and password and try to click the connect button. Steps to Reproduce: 1. Left click at the NM icon. 2. Choose "Connect to Other Wireless Network..." 3. Set any network name 4. Choose "Dynamic WEB (802.1x)" 5. Set authentication to "Tunneled TLS" 6. Set inner authentication to PAP 7. Fill in username and password. 8. you cant connect. Actual results: Cant connect because of that disabled connect button. Expected results: An enabled connect button if username and password are entered. Additional info:
I assume you are not choosing a CA certificate? Do you want to ignore verification of the RADIUS server's certificate? The applet currently requires a CA certificate but I'm thinking of changing this to just nag you with a "this isn't really secure, are you sure" instead of requiring one.
You are completly right, CA certificates are not used for verification by the wlan I am accessing. Would be great for a lot of students here if you could build in this nag.
+ 1 on not forcing it.
Working on this now
*** Bug 364021 has been marked as a duplicate of this bug. ***
NetworkManager-0.7.0-0.6.6.svn3109.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'
Now nm-applet crashes with the following error. (started from command line, after updating with testing rpm and restarting NM service) ** ERROR **: file eap-method-ttls.c: line 210 (nag_user): assertion failed: (dialog) aborting...
Accespoint config: dynnamic WEB - TTLS PAP - no certificate
NetworkManager-0.7.0-0.6.6.svn3109.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
I see the update has been pushed to stable update, but for my college Dave the problem still exists with NetworkManager-0.7.0-0.6.6.svn3109.fc8, see comment 7 and 8.
I got a backtrace from somebody, will work on that today. Need to be able to reproduce; but bodhi pushes updates out when they get 3 karma or more or something like that. The update doesn't make the problem _worse_ so I think that's a fair tradeoff for the moment. Thanks for reopening.
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'
I tried the update and it no longer crashes but still doesn't connect with dynamic wep (TTLS and PAP) Under F7 it used to work. I can connect with wpa_supplicant using the following commands: wpa_supplicant -Dwext -ieth1 -c /etc/wpa_supplicant/wpa_supplicant.conf Config file (wpa_supplicant.conf): ctrl_interface=/var/run/wpa_supplicant eapol_version=1 network={ ssid="HHS-802-1x" scan_ssid=1 key_mgmt=IEEE8021X eap=TTLS phase2="auth=PAP" identity="xxxxxxx" password="xxxxxxx" }
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Note this still does not work with my work's WLAN (tested using a college's (Dave's) laptop. The connect button works now and it no longer crashes, but it doesn't connect (which used to work with Fedora 7, and works with wpa_supplicant from the cmdline). See comment #13, reopen or should we create a new bug for this?
(In reply to comment #15) > Note this still does not work with my work's WLAN (tested using a college's > (Dave's) laptop. The connect button works now and it no longer crashes, but it > doesn't connect (which used to work with Fedora 7, and works with wpa_supplicant > from the cmdline). See comment #13, reopen or should we create a new bug for this? > For me this did not work until NetworkManager-0.7.0-0.6.7.svn3204.fc8 (grabed from koji) you will need a libnl and libdhcp update. But now I can connect to dynamic wep/ttls with mschapv2.
Ah, svn3204 being in tested was never added as a comment to this bug, however svn3204 + the new libnl and libdhcp from updates-testing also fixes wireless through networkmanager here, Thanks!