Description of problem: When I try to connect to our wireless network at work, the NetworkManager applet will not let me configure a connection with dynamic wep. After filling out all the required information, the connect button remains grey. Version-Release number of selected component (if applicable): 0.7.0-0.6.7.svn3235.fc8.x86_64 How reproducible: Select the network to connect to. Select dynamic wep in the popup that comes up. Fill in identity, user cert, ca cert, and key cert. As soon as any information is entered, the connect button turns grey. Even after specifying all required data, the button remains grey. Steps to Reproduce: 1. 2. 3. Actual results: Unable to save network information and connect Expected results: Network information entered and stored Additional info: I am able to manually connect using wpa_supplicant. The wireless network at work is using a hidden SSID and since we are using Cisco access points, the same access point is broadcasting another public SSID that does not use encryption for use by visitors. The non-guest wireless network uses IEEE8021X key management and requires a certificate to authenticate. When the network manager applet config screen comes up and dynamic wep is selected, the connect button turns grey after entering the first character in the identity field. I am using the b43 module and the wireless card in my laptop reported by lspci is: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
What format are your certificate files in? PEM or DER format? Did you enter the private key password at all?
The CA cert and user/key cert are in PEM format. Yes, I entered a private key password as well.
Any additional information needed?
As a side note, I also have /etc/dhclient-exit-hooks making some dynamic updates to our dns servers every time an ip address is leased. This works fine when ifup is used to manage networking, but does not seem to work when NetworkManager is used.
What are the filenames of your user and CA certificates and your private key? Can you paste in the successful wpa_supplicant configuration block you're using?
network={ ssid="mlkneap1" scan_ssid=1 key_mgmt=IEEE8021X eap=TLS identity="<HIDDEN>" ca_cert="/etc/pki/tls/certs/cacert.pem" private_key="/etc/pki/tls/certs/csbmwcert.pfx" private_key_passwd="<HIDDEN>" } I've also used openssl to convert and create a .pem version of the private key as well. Neither seems to work in NetworkManager. Brian
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.