After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734021 - nm-applet should support static address configuration together with dhcp/auto
nm-applet should support static address configuration together with dhcp/auto
Status: RESOLVED DUPLICATE of bug 763937
Product: NetworkManager
Classification: Platform
Component: nm-applet
unspecified
Other Linux
: High critical
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
: 632971 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-07-31 06:46 UTC by Juan Antonio
Modified: 2016-09-28 09:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Juan Antonio 2014-07-31 06:46:15 UTC
If I configure static params in a network profile (either wifi or ethernet), and later I select dhcp without clean the param fields, the network adapter takes the both configs, dhcp and static, with gateway of the static "disabled" config.

The issue doesn't dissapear after reboot, it's hold on and I have to select static ipv4 config, and clean all param fields and then select dhcp.
Comment 1 Bastien Nocera 2014-08-07 16:37:43 UTC
I don't understand what you're doing, or how you're doing it, or what you expect to happen. Please put in the full details of how to reproduce your problem, with screenshots if necessary.
Comment 2 Bastien Nocera 2014-08-10 15:12:39 UTC
*** Bug 734337 has been marked as a duplicate of this bug. ***
Comment 3 Bastien Nocera 2014-08-10 15:14:13 UTC
Bug 734337 has a better explanation of how to reproduce the problem:
--8<--
1. Change me wired network from DHCP to a static one (address, mask and
gateway)
-> did some work
2. Change back my network to DHCP

And here the problem began as the route stays locked to the one I previously
entered for the static config.
--8<--

Looks like the route isn't fetched again from DHCP?
Comment 4 Thomas Haller 2014-08-11 12:13:46 UTC
As I understand it, this is entirely an UI bug. So, it depends on which UI you are using.


Note that NM support does using dhcp *and* static addresses together and it works how you would expect: dhcp *and* static addresses are both assigned.


I agree that the UI either should expose all this functionality, or it should provide a consistently simplified subset of the full possibilities.


(1) In case of nm-applet (nm-connection-editor), if you had static addresses and switch to "auto" all addresses will be cleared and that configuration elements are disabled.
The only inconsistency for nm-applet happens if you edit a connection that has "auto" and static address configuration. In that case the static addresses are not displayed and you would not see them in the UI. Only when you modify&save the connection, the static addresses will be cleared out.
Maybe nm-applet should not disable the static address configuration and provide the full flexibility(?).


(2) gnome-control-center however does not clear the addresses when saving, but it does not show them either. So the situation here is worse because you think you are saving a purely auto connection, but the static addresses are not cleared.


I reassign the component of this bug to address (1).
I would reopen the duplicated 734337 to address (2) in gnome-control-center.
Comment 5 Thomas Haller 2014-08-11 12:36:09 UTC
Change the subject from:
  "network manager applet use static ipv4 params even using dhcp"
to:
  "nm-applet should support static address configuration together with dhcp/auto"


Maybe we don't want to support such a configuration in nm-applet. However, when editing such a connection, it must be indicated to the user that the connection has some static addresses.
Comment 6 Pavel Simerda 2014-11-23 19:06:01 UTC
I'm generally for supporting static addresses with auto even in nm-applet.
Comment 7 Thomas Haller 2015-02-23 16:06:11 UTC
*** Bug 632971 has been marked as a duplicate of this bug. ***
Comment 8 Beniamino Galvani 2016-09-28 09:17:09 UTC
Fixed in bug 763937.

*** This bug has been marked as a duplicate of bug 763937 ***