Created attachment 689257 [details] Correct entry of a static IP, netmask (/21) and proper gateway IP Description of problem: Final anaconda for F18 does not properly accept and reflect a valid GATEWAY within a /21 netmask Version-Release number of selected component (if applicable): How reproducible: Working through IP assignmane, as Manual, and with a 255.255.248.0 netmask Steps to Reproduce: see attached screenshots -- default device IP is not carried in to the parent screens Actual results: Expected results: Additional info: screenshots in a moment
Created attachment 689260 [details] does not pick up the gateway IP in the GUI interface display
Please note that the parent screen shows current IP configuration of a device. After changing and saving (persistent) configuration of the device in Connection Editor ([Configure] button), the device has to be reactivated (switched off and on) to apply the new configuration, which should be reflected in the parent screen then. Does this work for you?
umm -- I had manually set the IP to a value NOT .227 (the .227 was allocated by dhcp) ... when the MANUAL is selected, it really needs to no longer display the old values (blank and send a refresh event) ... it seems like the code is picking up seemingly raandom PARTS of the changes -- It sees and reflect the DNS server changes and the NETMASK, but NOT the IP, nor the default route It just seems like a 'refresh event' should be issued when re-entering the parent screen, and when changing method (why: MANUAL" rather than the more technically customary 'STATIC' which the config file parser ** understands ** ), and get 'all or none', not just 'parts of ... ' a change It just seems 'half done', don't you agree?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.