dhcp <--> static ip doesn't change when changing location

More information is needed.
What version of Ubuntu are you using.
Do you mean changing location in System -> Administration -> Networking?

i'm using 6.10
yes i use System -> Administration -> Networking to change location.
after location change i have to go for eth1 interface preferences and
manualy do ip setting.

2006/11/27, Pascal De Vuyst <email address hidden>:
> More information is needed.
> What version of Ubuntu are you using.
> Do you mean changing location in System -> Administration -> Networking?
>
> ** Changed in: Ubuntu
> Status: Unconfirmed => Needs Info
>
> --
> dhcp <--> static ip doesn't change when changing location
> https://launchpad.net/bugs/73358
>

Assigning to gnome-system-tools.

I don't have this problem on my Edgy PC with my wired Ethernet card and 2 locations configured: static and dynamic.
Please attach your /etc/network/interfaces.
Do you have network-manager installed?
Gnome-system-tools in Edgy is not compatible with network-manager.

please find what Synaptic says on network-manager:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
network management framework daemon
version: 0.6.3-2ubuntu6

network management framework (GNOME frontend)
version: 0.6.3-2ubuntu6
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

please also find inline /etc/network/interfaces as following
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

iface eth1 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
wireless-essid 52643541
wireless-key s:betko

auto eth1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2006/11/27, Pascal De Vuyst <email address hidden>:
> I don't have this problem on my Edgy PC with my wired Ethernet card and 2 locations configured: static and dynamic.
> Please attach your /etc/network/interfaces.
> Do you have network-manager installed?
> Gnome-system-tools in Edgy is not compatible with network-manager.
>
> ** Changed in: gnome-system-tools (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> dhcp <--> static ip doesn't change when changing location
> https://launchpad.net/bugs/73358
>

Where do you click to change the profile? How did you store your profile? Could you attach the profiles from .gnome2/network-admin-locations/* to the bug?

i go for System -> Administration -> Networking, then i click on
location selection on the top, then i pick needed location then i
click ok (actually green V). after location is loaded i highlight eth1
interface and click Properties. then i chose static ip or dhcp
depending on location.

i have stored locations by clicking save button (Save current network
configuration as a location).

2006/11/28, Sebastien Bacher <email address hidden>:
> Where do you click to change the profile? How did you store your
> profile? Could you attach the profiles from .gnome2/network-admin-
> locations/* to the bug?
>
> ** Changed in: gnome-system-tools (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
>
> --
> dhcp <--> static ip doesn't change when changing location
> https://launchpad.net/bugs/73358
>

~/.gnome2/network-admin-locations/biuras:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[general]
hostname=x60s
domainname=
dns-servers=212.59.0.1,212.59.0.2,
search-domains=
static-hosts=

[eth0]
auto=false
active=false
configured=true
config-method=2
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[eth1]
auto=true
active=true
configured=true
essid=52643541
key=betko
key-type=0
ip_address=192.168.1.2
ip_mask=255.255.255.0
gateway-address=192.168.1.1
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~/.gnome2/network-admin-locations/namai:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[general]
hostname=x60s
domainname=
dns-servers=212.59.0.1,212.59.0.2,
search-domains=
static-hosts=

[eth0]
auto=false
active=false
configured=true
config-method=2
ip-address=
ip-mask=
gateway-address=
network-address=
broadcast-address=

[eth1]
auto=true
active=true
configured=true
essid=52643541
key=betko
key-type=0
ip_address=192.168.1.2
ip_mask=255.255.255.0
gateway-address=192.168.1.1
network-address=
broadcast-address=

[ppp0]
auto=false
active=false
configured=false
login=
password=
phone-number=
phone-prefix=
default-gw=false
peer-dns=false
persistent=false
peer-noauth=false
serial-port=
volume=3
dial-type=1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It looks like config-method is not saved for your wireless connection eth1.

You could try to manually edit ~/.gnome2/network-admin-locations/* and add:
config-method=1 to [eth1] for location with static IP
and:
config-method=2 to [eth1] for location with dynamic IP (DHCP)

No reply, bug closed. Feel free to reopen with the asked informations if you still get that problem

Sebastien,

Arturasm has provided the necessary information, why do you close this bug as Rejected?

Pascal, your comment looked like something to try and to comment about which he didn't, if you look after that bug and can confirm it maybe you could forward it upstream with a brief summary on how to trigger it? Thank you for your bug work!

Upstream has abandoned g-s-t:
"Mass closing of remaining disks-admin and boot-admin bugs, sorry for the spam.
Both tools are bitrotting, and no development is likely to happen on them."

Double sorry, wrong bug...

Closing this report since nobody has answered to the questions Sebastien did, feel free to re open it if you are willing to send it upstream and can provide all the information in order to fix it. thanks in advance.

As i filed this bug in bugzilla, I also got this issue. http://bugzilla.gnome.org/show_bug.cgi?id=537924

Please describe the problem:
When changing location, with location A set to static ip, location B to dhcp,
it does not automatically retrieve a new ip address for location B.
You need to manually run sudo /etc/init.d/networking restart

Steps to reproduce:
1. Go to NM applet
2. Set current settings to static ip
3. press the "save current configruation as a location", name it 'config A'
4. Set current settings to a dhcp ip
5. press the "save current configruation as a location", name it 'config B'
6. select location 'config A' from the list
7. select 'apply configuration as current location'
8. press close
9. check that your ip is set to the static ip you've setup. This will be the
case
10. Go to NM applet
11. Select 'config B' as a location
12. select 'apply configuration as current location'
13. click close

Actual results:
you'll see that your router does NOT automatically give you a new ip. The
command sudo /etc/init.d/networking restart must be run

Expected results:
The program should automatically run the command 14. The command sudo
/etc/init.d/networking restart

Does this happen every time?
Yes

Other information:

As describe in my post, this is my second config file:

I do configrm that this bug exists.

I am using Ubuntu 8.10 and having the same problem. When I am tryinh to chahnge from DHCP to static IP address via Graphic User Interface the IP address is still the same, but when I am trying to modifit /etc/network/interfaces file everyting seems to be ok.

Stijn Gysemans,
This appears to be a different problem than originally reported, it is better to open a new bug report to avoid confusion.
Please note that the problem you describe occurs in network-admin that is part of gnome-system-tools and NOT in NetworkManager, so file the bug against gnome-system-tools and attach your location setting config files again.
Please also mention the version of gnome-system-tools or Ubuntu you are using.

This bug has originally been reported against gnome-system-tools 2.15.5 in Ubuntu Edgy.
A lot of changes have been made in gnome-system-tools since then. Furthermore Ubuntu Edgy is no longer supported (End of Life). Therefore we are closing this bug, please open a new bug report if you still have a similar problem in Ubuntu 8.04.1 LTS or later.

The new bug has been reported as per advice:
https://bugs.launchpad.net/ubuntu/+bug/312387