[network-admin] net-mgr doesn't remember location

This is a bug in g-s-t's network configuration tool. Reassigning.

the way network-admin apply profiles has been reworked on edgy, it would be interesting to try with the new version if you still get that problem

Thanks.

I'm sticking with Dapper until the next LTS, I think.

But I'm glad to hear things are progressing.

Have a great day.

Coby
> ----- Original Message -----
> From: "Sebastien Bacher" <email address hidden>
> To: <email address hidden>
> Subject: [Bug 74454] Re: [network-admin] net-mgr doesn't remember location
> Date: Sun, 14 Jan 2007 11:36:45 -0000
>
>
> the way network-admin apply profiles has been reworked on edgy, it would
> be interesting to try with the new version if you still get that problem
>
> ** Summary changed:
>
> - net-mgr doesn't remember location
> + [network-admin] net-mgr doesn't remember location
>
> ** Tags added: network-admin
>
> ** Changed in: gnome-system-tools (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs
>
> --
> [network-admin] net-mgr doesn't remember location
> https://launchpad.net/bugs/74454

>

--
_______________________________________________
Get your free email from http://e-mail.peru.com

I'm using "edgy-proposed" repository and after install I "apt-get update;apt-get upgrade" and the "network-admin" location stop working.

Right now I can't save any location and can't load the locations that I have in "~/.gnome2/network-admin-locations" (those locations were saved before upgrade)

Salute
Frank Abel

I've did a network configuration and store it as 'home'. Someday I manually add another dns plus the detected from the dhcp server.
Other time I delete that dns, so there was only 1 dns from dhcp server.
From time to time (less than 1 hour) the 'phantom' dns appears. so i have to delete it again.
After a couple of days i delete the location 'home'. And the phantom dns appears again.
Then I've created a new location: 'newone'. Guess wath? The phantom dns appears again!
Everytime the phantom dns appears in network-admin it's in /etc/resolv.conf too, and the location goes blank.
If i select the 'newone' location, the settings are taken from the saved ones. And the phantom dns goes away... just for a couple of minutes!
Any idea?

I'm not sure why I got this question. I am a user, a bug-reporter, not
a developer. Asking me why this went wrong is like network-admin asking
more than one conffile--even if those files conflict--what the DNS
configurations are. It obviously does, and I obviously was asked. I
guess they have done a better job with this in Feisty. For now, I have
scaled back my expectations of network-admin and just keep it simple.
Hope you fare as well.

Me sorprende que esta pregunta me llegara a mí, un simple usuario, un
reportador de errores, y no un desarrollador. Será que desde que he
reportado el error, mi nombre aparece en alguna lista... El
network-manager de igual modo parece hacer sus preguntas a archivos que
no debe, y hasta hay conflictos en la información que agarra de ellas.
Ah, así es la vida. Me contaron que en la Feisty hicieron cambios muy
favorables relacionados a esta cuestión. Yo por ahora no espero más que
el network-mgr me conecte al internet. Espero que las cosas le salgan
mejor para vos.

Gracias,

Coby

Thanks,

Coby

On Tue, 2007-02-13 at 20:30 +0000, parq wrote:
> I've did a network configuration and store it as 'home'. Someday I manually add another dns plus the detected from the dhcp server.
> Other time I delete that dns, so there was only 1 dns from dhcp server.
> >From time to time (less than 1 hour) the 'phantom' dns appears. so i have to delete it again.
> After a couple of days i delete the location 'home'. And the phantom dns appears again.
> Then I've created a new location: 'newone'. Guess wath? The phantom dns appears again!
> Everytime the phantom dns appears in network-admin it's in /etc/resolv.conf too, and the location goes blank.
> If i select the 'newone' location, the settings are taken from the saved ones. And the phantom dns goes away... just for a couple of minutes!
> Any idea?
>

Posting here in hopes of getting this bumped to a higher priority; not sure it's the same bug but the title is exactly acurate:

I am running Ubuntu 7.04 (Feisty Fawn)
to reproduce:

- open network-admin
- (optional, I think) change some settings (for example, I've specified an alternate DNS server)
- click the save button next to the "Location" drop down menu; type a name and click 'Save"
- reboot

When you open network manager again, the location will be blank, and the settings will have gone back to defaults (from dhcp I suspect). Choosing the saved location does change the settings as expected, but this is a hassle to have to do every time the computer is booted.

Alternately, instead of rebooting, you can close network-admin and just run 'sudo dhclient' and it will clear the Location.

Expected behavior would be that one could choose a default location, or the last used location and settings would be used.

I am having precisely the same problem as Bjorn Hansen. Is there no way of voting for a bug to increase its priority?

I've nominated it for fixing in Feisty and Gutsy, so maybe that will help? (If someone could tell me the source package, I may be able to develop a patch.)

Glyn, thank you for your interest. What do you want to achieve by nominating the bugs for Ubuntu versions? The problem is that the desktop teams has just a lot to do, the best way to get the bug fixed faster is to give a hand. The package you want to change is likely gnome-system-tools, maybe Carlos can give extra precisions on the code though

Hi Sebastien

I figured that since the bug tracker doesn't have a way of voting for bugs, that was the only lever available to flag the importance of the bug. I have been delighted by Feisty and this particular bug stands out compared to the usability of the other parts of the system I have used.

I admit I was surprised to be allowed to nominate the bug for a version - maybe that's something that should be restricted to committers?

Anyway, thanks for the pointer to the source...

the bugs can be nominated by anybody, they need to be accepted then

I did a bit more investigation of the problem to see if it could be patched. /etc/resolv.conf appears to be the definitive place where the network settings are stored. This file starts with:

# generated by NetworkManager, do not edit!

I checked the source of gnome-system-tools with:

grep -R NetworkManager *

and found no instances, so I guess the file must be written by another component, such as dhcp. This is true even when network-admin is used to change the settings. Clearly more investigation is required, but I thought I'd mention this in case anyone else is thinking of developing a patch. (I have found a very satisfactory application-specific workaround, so my motivation is waning.)

There hasn't been any recent activity in this bug for a while. Just curious if this is still an issue in the latest Hardy Alpha release? Thanks.

Hi there
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with development version of Ubuntu, Hardy Heron?

Thanks in advance.

I am experiencing what appears to be the same problem.

The network-admin has an unnamed default location. I have a saved location that has my correct DNS settings. However every time that I restart my computer the settings revert to the unmaned location. That means I need to do a manual configuration every time I restart.
I am using Ubuntu 7.10 Gutsy Gibbon

I think that I have may have found the answer to my problem.
This thread talks about a DHCP server having an incorrect DNS setting.
https://answers.launchpad.net/ubuntu/+question/3674

I tried rebooting while my DHCP server was switched off. in that case I noted that /etc/resolv.conf had the expected values and network-admin had my desired location.
However once the DHCP server (http://pigtail.net/LRP/index.html) finished booting the DNS values were set to dud values and network-admin changed to using an unnamed location.

Just a helpful FYI although I am no longer using a network:

I think I remember discovering this quirk in my Dapper system when I was
manually setting domains. I remember DHCP wasn't working best for me.

Is it possible that the gap in logic is not in DHCP but in a library it
uses? That gets used even when it is off?

Thanks,

Coby
<email address hidden>

On Sat, 2008-04-05 at 10:37 +0000, Keith Morris wrote:

> I think that I have may have found the answer to my problem.
> This thread talks about a DHCP server having an incorrect DNS setting.
> https://answers.launchpad.net/ubuntu/+question/3674
>
> I tried rebooting while my DHCP server was switched off. in that case I noted that /etc/resolv.conf had the expected values and network-admin had my desired location.
> However once the DHCP server (http://pigtail.net/LRP/index.html) finished booting the DNS values were set to dud values and network-admin changed to using an unnamed location.
>

I did not add enough about my set up in the last post.
I am using an old computer as a hardware firewall and DHCP server. The Network Settings (network-admin) was getting the incorrect values from my DHCP server. Once I fixed that DNS server IP addresses on my DHCP server the issue of "lost location" was not causing me DNS setting headaches.

HOWEVER, Network Settings still does not show a value in "Location". It would be useful for the Network Settings to indicate that the setting have come from an outside source. This would then cause less confusion as to why the location is not set.

Thanks
Keith Morris

I've run into this issue in 8.4. When I reboot, it sets my default back to the unnamed default, not my created profile. Please let me know what needs to be done for this bug to get it brought back to life.

Bumping back to new, as no one has stated why this bug is incomplete.

not sure how voting works or if there is any but ... hear hear! I am not sure if Network Manager never saves location or if it depends on the setup but:
1) there is no way (that I know of) to add details (like domain resolution) without working with locations
2) there is no way (that I know of) to make location default or to make it 'autorecognize' by subnet or something.

So at the moment I do use location and I have to set location every time I reboot (or go into suspend, I think it resets then too, suspend stopped working with Heron so I can't test)

I will look into source but... I am pretty lame with linux/C++ :(

I can confirm this bug in Xubutnu 8.04 with all the latest updates. If you are using DHCP, network-manager retrieves the configuration for your network from the daemon using the settings in /etc/dhcp3/dhclient.conf. You can see the load functionality in /var/log/daemon.log

daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) started...
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Old device 'eth0' activating, won't change.
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
daemon.log.0:Jun 19 22:45:29 blackbox NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
daemon.log.0:Jun 19 22:45:30 blackbox NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
daemon.log.0:Jun 19 22:45:30 blackbox NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
daemon.log.0:Jun 19 22:45:30 blackbox NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0
daemon.log.0:Jun 19 22:45:32 blackbox NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth0
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> address 10.2.10.2
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> netmask 255.255.255.240
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> broadcast 10.2.10.15
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> gateway 10.2.10.1
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> nameserver 207.69.188.185
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> nameserver 207.69.188.186
daemon.log.0:Jun 19 22:45:33 blackbox NetworkManager: <info> nameserver 207.69.188.187
daemon.log.0...

This is the intended actions of the Network Manager as per the man page:

       The NetworkManager daemon attempts to keep an active network connection available at all times.
       The point of NetworkManager is to make networking configuration and setup as painless and automatic
       as possible. If using DHCP, NetworkManager is intended to replace default routes, obtain IP
       addresses from a DHCP server, and change nameservers whenever it sees fit, with the aim of making
       networking Just Work.

I'd say this WASN'T the intended action of Network Manager which (according to the man page you cite) is "making networking Just Work." This interaction makes networking Just Fail and for no apparent reason.

It is a bug: a logical consequence of the code that was written that, for unforeseen reasons, works AGAINST the goals of the program. It's doing what they said, but not what they wanted.

NetworkManager, if it is to be more useful than annoying, needs to recognize when the user makes changes to the network and have some why to preserve those, rather than just playing "mama knows best" and ignoring use specified configuration information.

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

Pedro--

The network manager interface has changed so much since Dapper, I
don't have any idea if this is still a problem. Now all I do is share
folders with Samba and printers with CUPS (except that isn't working
right...another story). Instead of the network manager I use folder
sharing options, which seems to work. Point of fact, I've stayed away
from using network profiles, assuming that it's a poorly supported
feature.

And I've been using Natty since December. What was Dapper, 6.04?
That's been a while!

Thanks,

Coby

2011/5/19, Pedro Villavicencio <email address hidden>:
> Thanks for the report, it has been some time without any response or
> feedback in this bug report and we are wondering if this is still an
> issue for you with the latest release of Ubuntu the Natty Narwhal, May
> you please test with that version and comment back if you're still
> having or not the issue? Please have a look at
> http://www.ubuntu.com/download to know how to install that
> version.Thanks in advance.
>
> ** Changed in: gnome-system-tools (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/74454
>
> Title:
> [network-admin] net-mgr doesn't remember location
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/74454/+subscribe
>

[Expired for gnome-system-tools (Ubuntu) because there has been no activity for 60 days.]