nm-connection-editor changes doesn't persist

Bug #281687 reported by Ricardo Pérez López on 2008-10-11
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Undecided
Unassigned

Bug Description

Precondition: You need to have a working DHCP wired connection.

Steps to reproduce:

1. Right-click on nm-applet icon, select "Edit Connections".
2. Select the wired connection (mine is named "Auto eth0"). Click on Edit.
3. Check that "Connect automatically" and "System setting" are enabled.
4. Select "IPv4 Settings" tab.
5. Change Method from "Automatic (DHCP)" to "Automatic (DHCP) addresses only".
6. Set DNS Servers to "80.58.0.33,80.58.0.97".
7. Click on OK, and then click on Close.
8. Reboot the computer.
9. Go again to "Edit Connections"->Edit->IPv4 Settings

Expected behavior: The method still is "Automatic (DHCP) addresses only", and the DNS Servers still are "80.58.0.33,80.58.0.97".

Actual behavior: The method is "Automathic (DHCP)" and there is no DNS Servers. If you do:

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 62.42.230.24
nameserver 62.42.63.52

That way, I can't manually set the DNS servers of my Internet connection, because their values doesn't persist in NetworkManager.

Filipe Sousa (natros) wrote :

My problem is when I change from Automatic (DHCP) to manual. After a reboot the configuration remains Automatic (DHCP).

Ricardo Pérez López (ricardo) wrote :

Confirmed by another user.

Changed in network-manager-applet:
status: New → Confirmed
Pat Double (patdouble) wrote :

I have a similar issue with the "System Setting" flag. If I edit a wireless connection to make it a system setting and click OK, the flag never gets changed. I find no entries in /etc/NetworkManager/system-connections. There is no output in /var/log/syslog when this happens. My wireless connection is using a WEP key and works for my user, but I would like it to work for all users.

Ilya Barygin (randomaction) wrote :

There is a similar bug 259214 (may be the same problem).

Alexander Sack (asac) wrote :

259214 is a catch all bug. I think bug 293820 might also be worth a look.

Vitor Lamas Gatti (vitorgatti) wrote :

I can confirm this bug. Please, fix this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers