Red Hat Bugzilla – Bug 494770
Cannot change connection settings
Last modified: 2009-04-09 09:39:11 EDT
Description of problem:
NetworkManager won't let me change any connection settings. When I click on "Edit" for a connection, all the buttons and fields on all the tabs are grayed out.
Version-Release number of selected component (if applicable):
Reporter, could you please say us if you have the problem only on wireless or wired network tabs or both?. If you try to add an Network, are there also all buttons grayed out? Thank you.
Fedora Bugzappers volunteer triage team
It's just the wired network tab.
The buttons are not grayed out when I go to add a connection.
The connection you are attempting to edit is a "system" connection, which is read-only at this time. You can create a new connection with the "Add" button and configure that as you like. Let me know if that doesn't work for you.
In that case, NetworkManager has erroneously configured the "system" connections to use DHCP. Is there really no way to correct this?
I am able to add another connection; however, I have not found a way to make NetworkManager use the added connection by default. NetworkManager reverts to using one of the "system" connections when the machine is restarted.
Reopening. There is definitely a bug here; though I'm no longer sure exactly what it is.
Does it look like this? Can you post a screenshot of your "wired" tab?
Created attachment 338856 [details]
Network Connections dialog screen shot
It looks like this.
This machine has two wired NICs; which apparently correspond to "System eth0" and "System eth2". (Why "eth2" and not "eth1", I'm not sure.) Upon startup, NetworkManager always connects using "System eth0". Both "System eth0" and "System eth2" are configured to use DHCP and there appears to be no way to change that.
"Wired connection 1" is the connection I added. I am able to configure it as I like. However, I had to set it up using the same MAC address as "System eth0". I don't know if that's a bad thing or not; but it feels funny.
From 10,000 ft, the problem here is this: NetworkManager starts up using a DHCP connection when it should be using a static IP.
Okay... Part of the issue here has been a lack of understanding on my part regarding the relationship between NetworkManager and the "classical" network interface scripts (configured by system-config-network). I had been under the impression that these were two separate worlds--and that appeared to be the case until relatively recently.
So now, I take it, the "system" connections are configured by system-config-network; and NetworkManager is currently incapable of modifying these interfaces (caveat bug 495027).
So if this is, in fact, "working as intended", I guess we're done here. Though clearly the current NetworkManager/system-config-network dichotomy has *serious* usability flaws.
(In reply to comment #8)
> Okay... Part of the issue here has been a lack of understanding on my part
> regarding the relationship between NetworkManager and the "classical" network
> interface scripts (configured by system-config-network). I had been under the
> impression that these were two separate worlds--and that appeared to be the
> case until relatively recently.
> So now, I take it, the "system" connections are configured by
> system-config-network; and NetworkManager is currently incapable of modifying
> these interfaces (caveat bug 495027).
Currently, but that capability is planned for F11 and is being worked on in a branch upstream:
> So if this is, in fact, "working as intended", I guess we're done here. Though
> clearly the current NetworkManager/system-config-network dichotomy has
> *serious* usability flaws.
Yes, it does; those are actively being rectified.