[network-admin] bug with several location in System->Networking (network-admin)

Bug #54478 reported by Alexej Perevalov
4
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

I have been install Ubuntu 6.06 LTS from skretch.
At work my ip address is 192.168.0.12
I have been use network-admin(Сетевые настройки) for configure it. Yes, default language is RUSSIAN, locate - UTF-8.

I selected network-admin form system menu.
Than, in network-admin i select "Create Location" (Создать новое расположение"), enter name "xring" in ENGLISH.
Than i click ETHERNET, PROPIERTIES, and enter ip, gataway, mask,
than i enter DNS.
OK.
ALL work fine. IN file /etc/network/interfaces
--******************************-- BEGIN
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
-***********************-- END
/etc/resolv.conf
nameserver 192.168.0.1

ALL WORK FINE

At home, my ip address is 10.33.24.58
I have been create new location, named "moscow_home",
select "Ethernet connection", click Properties, fill all fields,
enter DNS. click OK.
in console, $>ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:00:9B:18:8C
          inet addr:10.33.24.58 Bcast:10.33.24.255 Mask:255.255.255.0
          inet6 addr: fe80::2e0:ff:fe9b:188c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:3268171 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23145 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:232698510 (221.9 MiB) TX bytes:2808445 (2.6 MiB)
          Interrupt:10 Base address:0x4000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:61 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4272 (4.1 KiB) TX bytes:4272 (4.1 KiB)

--ALL WORK FINE
BUT in interfaces still 192.168.0.1 ??????
CLOSE NETWORKING.

I GOTO TO MY WORK. booting, current ip adress 10.33.24.58, i launch SYSTEM->Networking, select "xring", current ip 192.168.0.1
ALL WORK FINE.
BUT AT HOME when i select "moscow_home" current ip address still was 192.168.0.1, i lick OK, i lauched Networking again, location field was blank, i select "moscow_home", click PROPERTIES, and ip address was 192.168.0.1 and ather field the same with "xring" WHYYY???????
ifconfig shows wrong ip.
I reenter all field in "moscow_home" click ok.
ifconfig shows right ip.
I restart System->Networking (network-admin). I see blank location (current location is blank), i select moscow-home, and get wrong ip. Again all setting getting from "xring".
I remove "xring", reenter all "fields" in "moscow_home",
click OK, ifconfig shows right ip.
RELAUNCH network-admin, select "moscow_home" --- wrong setting, all settin from "xring", BUT it removed.
I see at /etc/gnome-system-tools/network/profiles.xml

<profiledb>
  <profile>
    <gateway>192.168.0.1</gateway>
    <gatewaydev>eth0</gatewaydev>
    <hostname>alexy-laptop</hostname>
    <name>moscow_home</name>
    <smbdesc>%h server (Samba, Ubuntu)</smbdesc>
    <smbuse>0</smbuse>
    <workgroup>MSHOME</workgroup>

    <nameserver>192.168.0.1</nameserver>

    <statichost>
      <ip>ff00::0</ip>
      <alias>ip6-mcastprefix</alias>
    </statichost>
    <statichost>
      <ip>127.0.0.1</ip>
      <alias>localhost</alias>
      <alias>alexy-laptop</alias>
    </statichost>
    <statichost>
      <ip>fe00::0</ip>
      <alias>ip6-localnet</alias>
    </statichost>
    <statichost>
      <ip>ff02::1</ip>
      <alias>ip6-allnodes</alias>
    </statichost>
    <statichost>
      <ip>ff02::2</ip>
      <alias>ip6-allrouters</alias>
    </statichost>
    <statichost>
      <ip>::1</ip>
      <alias>ip6-localhost</alias>
      <alias>ip6-loopback</alias>
    </statichost>
    <statichost>
      <ip>127.0.1.1</ip>
      <alias>alexy-laptop</alias>
    </statichost>
    <statichost>
      <ip>ff02::3</ip>
      <alias>ip6-allhosts</alias>
    </statichost>

    <interface type='modem'>

      <dev>ppp0</dev>
      <enabled>0</enabled>
    </interface>

    <interface type='loopback'>

      <configuration>
        <auto>1</auto>
        <bootproto>none</bootproto>
        <file>lo</file>
      </configuration>
      <dev>lo</dev>
      <enabled>1</enabled>
    </interface>

    <interface type='ethernet'>

      <configuration>
        <address>192.168.0.12</address>
        <auto>1</auto>
        <bootproto>none</bootproto>
        <file>eth0</file>
        <gateway>192.168.0.1</gateway>
        <netmask>255.255.255.0</netmask>
      </configuration>
      <dev>eth0</dev>
      <enabled>1</enabled>
    </interface>
  </profile>
</profiledb>

wrong ip was here.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Assigning to g-s-t...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. You probably have been confused by the way network-admin works on dapper.
When you add a profile it's created with the information you have at the moment. When you do changes, you don't modify the selected profile but the running session. To store the changes to add profile you have to add a profile with the same name. Reading that, do you think the tool works as described or do you still have some non expected behaviour from it?

The way the tool work on dapper is really not obvious and we worked with upstream to change that on edgy. Now the "add" button next to the profile has been changed to a "save" one which open a window asking for the name of the profile to use and the name is preset to the current profile. Do you think that behaviour change fixes your issue?

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Alexej Perevalov (pau-rusteko) wrote : Re: [Bug 54478] Re: [network-admin] bug with several location in System->Networking (network-admin)

В Сбт, 09/09/2006 в 12:12 +0000, Sebastien Bacher пишет:
> Thanks for your bug. You probably have been confused by the way network-admin works on dapper.
> When you add a profile it's created with the information you have at the moment. When you do changes, you don't modify the selected profile but the running session. To store the changes to add profile you have to add a profile with the same name. Reading that, do you think the tool works as described or do you still have some non expected behaviour from it?
>
> The way the tool work on dapper is really not obvious and we worked with
> upstream to change that on edgy. Now the "add" button next to the
> profile has been changed to a "save" one which open a window asking for
> the name of the profile to use and the name is preset to the current
> profile. Do you think that behaviour change fixes your issue?
>
> ** Changed in: gnome-system-tools (Ubuntu)
> Importance: Untriaged => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>

Thanks for your answer. I don't know have i last network-admin version
(network-admin --version Gnome network-admin 2.14.0). But it steel
buggy. By default i use setting from /etc/network/interfaces.
I don' run network-admin since i posted bug report.
But now i run it. There was one places moscow_home, i selected it (i
don't know what was in /etc/gnome-system-tools/networks/profile.xml),
but new ip address become another, from my old work. I fix it and add
new place "kafedra", i switch betwean places, all switching work, but
slowly, after restart network-admin, all ipaddress was permutated, avery
time then i change ipaddres of moscow_home, after restart network-admin
it steel old. It can't changed.

auto lo
iface lo inet loopback

iface eth0 inet static
address 10.0.0.5
netmask 255.255.255.0
gateway 10.0.0.1

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth0

Revision history for this message
Sebastien Bacher (seb128) wrote :

if you want to change moscow_home, you need to do your modifications and then add a profile named "moscow_home" again. Does it work this way?

Revision history for this message
Daniel Holbach (dholbach) wrote :

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

Changed in gnome-system-tools:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.