Bug 943 - Can't change ip-settings of interface with NetworkManager
: Can't change ip-settings of interface with NetworkManager
Status: RESOLVED WONTFIX
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
: ROSA 2012.1 Beta
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-16 11:38 MSD by FirstLevel
Modified: 2016-01-19 20:46 MSK (History)
4 users (show)

See Also:
RPM Package: networkmanager-0.9.6.0-1-rosa2012.1.i586
ISO-related:
Bad POT generating:
Upstream:


Attachments
eth0-dhcp.png (226.35 KB, image/png)
2012-10-16 11:38 MSD, FirstLevel
Details
eth0-dhcp1.png (227.78 KB, image/png)
2012-10-16 11:38 MSD, FirstLevel
Details
eth0-static.png (228.64 KB, image/png)
2012-10-16 11:38 MSD, FirstLevel
Details
eth0-static2.png (294.27 KB, image/png)
2012-10-16 11:38 MSD, FirstLevel
Details
eth0-static3.png (244.55 KB, image/png)
2012-10-16 11:38 MSD, FirstLevel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description FirstLevel 2012-10-16 11:38:01 MSD
Created attachment 700 [details]
eth0-dhcp.png

Description of problem:
0. Suppose You have DHCP on eth0
eth0-dhcp.png eth0-dhcp1.png
1. Open NM-widget. Click Manage connections.
2. Change IP configuration of connection.
eth0-static.png
3. Click Apply.
4. Nothing happens. You have old IP-configuration.
eth0-static2.png
5. But if You disconnect and connect eto0 from NM You see that new ip-cobfiguration is applying 
eth0-static3.png

btw. For ROSA 2012 LTS on the step 3 root password is needed. but for desktop root password is not requested.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 FirstLevel 2012-10-16 11:38:14 MSD
Created attachment 701 [details]
eth0-dhcp1.png
Comment 2 FirstLevel 2012-10-16 11:38:27 MSD
Created attachment 702 [details]
eth0-static.png
Comment 3 FirstLevel 2012-10-16 11:38:42 MSD
Created attachment 703 [details]
eth0-static2.png
Comment 4 FirstLevel 2012-10-16 11:38:55 MSD
Created attachment 704 [details]
eth0-static3.png
Comment 5 Postnikov Dmitry 2012-10-18 12:10:39 MSD
Similarly in 499th iso
After changing the settings, there is no auto-restart the network
Comment 6 Alexander Burmashev 2013-11-07 13:47:41 MSK
Is bug still valid ?
Comment 7 FirstLevel 2013-11-07 14:17:16 MSK
(In reply to comment #6)
> Is bug still valid ?

yes on the system with actual updates.
Comment 8 Aleksandr Kazantcev 2014-01-27 11:47:09 MSK
This is normal - change IP need restart NM and system. Close.
Comment 9 FirstLevel 2014-01-27 15:37:06 MSK
(In reply to comment #8)
> This is normal - change IP need restart NM and system. Close.

No it is not normal.  For all systems I could change ip-settings with some wizard without  any other interaction to system.
Why this wizard for NM could not restart appropriate service?
Comment 10 FirstLevel 2014-10-08 21:30:14 MSD
Case is actual for 2014.1
Comment 11 FirstLevel 2015-04-20 11:47:34 MSD
Case is actual for Fresh R5 and plasma-nm
Comment 12 Denis Silakov 2016-01-19 20:46:12 MSK
We are fine with the current behavior when to really apply IP change you should disable connection and enable it again indicating that you know what you are doing. 

Only if upstream developers decide to switch this behavior then we surely will switch it, as well.