[Hardy] Network monitor not saving settings

[stego]

Binary package hint: network-manager

Hello there!
  I was in process of setting up a Hardy system on my companys NON-DHCP network, and ran into the following bugs:

1) From a clean install: While setting up my IP information, I had initially forgotten to enter my DNS information (I found this out when I was able to ping other machines but couldnt ping yahoo.com). When I went back in to Enter the IP information, I entered it onto the blank line that was available, and clicked Close. I was still unable to ping, and when I checked the settings, the IP addressed that I entered for the DNS was not there. I attempted this a few times, each and every time resulted in the DNS ip not being saved. To get around this, I had to manually enter a nameservers entry in /etc/resolv.conf.

2) After updating the system to todays packages: I had noticed that the system was not connecting to the network. I checked the settings nder Network Manager, and it was showing the correct settings. I changed to Roaming mode, then changed back in hopes that the settings would take, it did not. I killed the network manager, and ran it under a terminal. I changed the IP address to another available IP, and it Finally took the change.

Suggestion: Add an APPLY button next to the Close button to force the settings to be written right then and there.

[stego (stego)]

Also!
  I just reset the machine: it does NOT apply the manual configuration settings at startup at all! I have to manually go back in and select a different IP address and apply the settings to get it to connect to the network.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your report would get better attention if you were to submit each bug individually as they deal with different packages and parts of the distribution. Part 1 sounds like a bug in gnome-system-tools, where you statically setup network connections. Part 2 sounds like a possible bug with network-manager. Which bug would you like this report to be about? Thanks in advance.

[stego (stego)]

Hello Brian!
  Thank you! Set this one to be Part 2: Where Network Manager is not connecting to a Static IP address properly upon reboot..

[Brian Murray (brian-murray)]

Could you add your '/var/log/syslog' file as an attachment to you bug report after ensuring it covers the time period in which you experienced the bug? Thanks again.

[Islam Badrel-Dein (islambadreldein)]

Hello

I can confirm this bug! I have to
$ sudo ifup eth0

EVERY TIME I startup Hardy because the network does not come up automatically. Also, another workaround is to change the IP address to something different than my actual IP, then change it back to my actual IP address so that the network could be configured properly. I think the network-manager does NOT save the settings correctly between reboots. It only saves it for the current session.

Thanks for your time...

[Islam Badrel-Dein (islambadreldein)]

Also, for the suggestion of stego, I don't think that adding an "Apply" button would solve the problem. The network-manager already applies any changes that I do 'on the fly' if I just waited idle for two or three seconds. The problem is NOT in the network configurations of the current session. The problem IS saving the network configurations between reboots.

[Pēteris Krišjānis (pecisk-gmail)]

This is dublicate of https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/185854