Red Hat Bugzilla – Bug 158495
DHCP selection unavailable when setting up multiple wireless profiles in neat
Last modified: 2008-02-11 18:44:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
While trying to setup multiple wireless network connection profiles in the Network Configuration GUI (neat) the configuration wizard is called normally. Selecting DHCP is successful in the wizard however, once the configuration completes, editing the profile that was just created shows that "Statically set IP addresses:" is selected and "Automatically obtain IP address setting with: dhcp" is unavailable to be selected. Note this problem is apparent only after having setup a profile that uses dhcp.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup a profile that uses DHCP
2. Attempt to setup another profile that uses DHCP, but say with no wireless encryption key
3. Complete the wizard and edit the new profile.
4. Notice that DHCP is not selected and cannot be changed from Static.
Actual Results: Wireless Device profile has "Statically set IP addresses:" selected despite having selected DHCP in the wizard. "Automatically obtain IP address settings with:" is grey and cannot be selected.
Expected Results: Profile should show "Automatically obtain IP address settings with: dhcp" selected. Also, ability to switch between Static and Automatic IP detection should be allowed.
This problem has occured using Cisco Aironet cards and Linksys cards but appears to be hardware independent. Copying an existing profile and editing it is a workaround.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.