Red Hat Bugzilla – Bug 819124
NetworkManager does not allow customizing broadband connection's parameters, making it unusable
Last modified: 2015-02-17 09:14:52 EST
Hello, Description of problem: I am using a ZTE HSUPA MF110 USB stick to connect to Internet, over RCS&RDS' "Digi Net Mobil" GSM service (Romania). Since my IP address is static, I need to configure a different APN in order to make the GSM connection to work. As of May 4th, 2012, in Fedora 17 beta, NetworkManager won't allow me to configure the APN, making the stick unusable. When attempting to configure the 3G broadband connection, the "Options" button is greyed out. Things went smoothly in previous versions of Fedora, including FC16, as well as in other distros (Ubuntu 11.10, 12.04). Version-Release number of selected component (if applicable): NetworkManager-0.9.4.0-8.git20120502.fc17.x86_64 How reproducible: Always. Steps to Reproduce: 1. Boot Fedora 17 beta and log in. 2. Insert MF110 USB stick and wait for the system to "see" it. The option to configure a 3G broadband connection appears in NetworkManager, asking for the name of the carrier, digital plan, etc. for the initial configuration 3. Note that there is no option to specify a different APN, a fixed IP address for the connection, DNS servers, etc. during the initial setup. 4. After configuring the connection with the default options, open the NetworkManager's menu (in Gnome, right-up corner) and try to customize the 3G connection (via the last option in the menu, "Network settings") 5. Note that one cannot enter customized parameters for the 3G connection; the only "Options" button is greyed out. Actual results: Cannot use the 3G connection because I cannot configure it correctly. Expected results: NetworkManager should offer a way to configure the 3G connection, with various parameters and add/delete carriers, multiple connections, etc. Regards, Răzvan
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.