[Feisty] network-admin forgets static in interfaces

Bug #80622 reported by Julien Lavergne
82
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned
gnome-system-tools (Ubuntu)
Invalid
Undecided
Unassigned
system-tools-backends (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

When I configure a static connection, network-admin forget "static" in the configuration /etc/network/interfaces :
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

iface eth0 inet
address 192.168.0.25
netmask 255.255.255.0
gateway 192.168.0.254

auto eth0

Adding "static" after "iface eth0 inet" solves the problem

Changed in gnome-system-tools:
status: Unconfirmed → Confirmed
Revision history for this message
iKs (iks279) wrote :

I can confirm this bug.
It seems it's a duplicate of bug 12074 and of bug 11976 but those bug are quite old : they were reported during January 2005... (and fixed)

I alos noticed network-admin added an "s:" in front of my WEP key wich made it ascii and not hexadecimal but maybe those two bugs are totally unlinked..

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

Probably similar to bug #82088 due to the network-manager roaming mode

Revision history for this message
Andrew Conkling (andrewski) wrote :

On 2/3/07, Sebastien Bacher <email address hidden> wrote:
> Probably similar to bug #82088 due to the network-manager roaming mode

That does look like the same effect, but (at least for me) it has nothing to do with network-manager. Because of the fact that I have a static IP, I don't run network-manager at all. (Apps that use it for network detection tend to get confused.)

Revision history for this message
Julien Lavergne (gilir) wrote :

I believe network-manager use network-admin for static IP no ? When I try to configure static IP with network-manager, I have the same problem : I must add the static to the interfaces file to have a connection. And after that, network-manager stay on a disconnected state (and many applications like epiphnay, evolution ... are on a disconnected state too ...).

Revision history for this message
Andrew Conkling (andrewski) wrote :

On 2/4/07, Julien <email address hidden> wrote:
> I believe network-manager use network-admin for static IP no ?

Yes, but since it's a separate tool, I'm pretty sure this bug does not necessarily depend on any use of network-manager at all.

Áron Sisak (asisak)
Changed in gnome-system-tools:
assignee: nobody → asisak
status: Confirmed → In Progress
Áron Sisak (asisak)
Changed in gnome-system-tools:
assignee: asisak → nobody
Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
importance: Undecided → High
Revision history for this message
Tcornishmn (tcornishmn) wrote :

I am confirming this bug as well - adding static to the end of the interface description in /etc/network/interfaces allows connectivity.

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

Same problem here. I have to edit /etc/network/interfaces at every startup to let the connections working.

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

Tom, if you have to edit at every startup that's probably not a network-admin bug, since it changes the configuration only when being used. Do you have network-manager running? That might be due to it

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

Yes Sebastian, you're right: if I disable the network-manager applet in startup programs the /etc/network/interfaces remains unchanged.

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

I can't understand if this is a network-manager problem or not.

The bug report still points to gnome-system-tools.

Revision history for this message
Áron Sisak (asisak) wrote :

I am almost sure, this is *not* a network-manager problem.
I don't use network-manager and the bug still occours.

Revision history for this message
Stephen Gornick (sgornick) wrote :

Problem persists for me in Feisty Herd-4

After changing to static ip address using network-admin:

$ grep eth0 /etc/network/interfaces
iface eth0 inet

Expected:
iface eth0 inet static

Revision history for this message
Alberto Stefani (endymion75) wrote :

Same problem here too.

After clear installation only DHCP work.

I set-up static IP by network-manager and close, reopen network-manager and "roaming mode" are enable.

I setup by "ifconfig" and my board only ping my router, no web, no ftp, no mail...etc...

I edit /etc/network/interfaces adding "static" and rebooted... now static IP work for me...

boh...

GNU/Linux Ubuntu Feisty Herd4

Revision history for this message
Martin Pitt (pitti) wrote :

For the record:
<garnacho> pitti: I've fixed that in CVS :)

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

That upload fixes the problem:

 system-tools-backends (2.1.3-0ubuntu2) feisty; urgency=low
 .
   * debian/patches/90_from_cvs_fix_static_interface.patch:
     - patch from CVS, fix "static" not being written to the interfaces file
       (Ubuntu: #80622)

Changed in gnome-system-tools:
status: In Progress → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

not a gnome-system-tools problem

Changed in gnome-system-tools:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

nor an Ubuntu one, and it's fixed

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

Yes, sorry. It was my fault. I messed up with the report. I was doing 5 different things at the same time and the result was this.

Sorry again :(

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

no problem, that was quick to fix

Revision history for this message
Stephen Gornick (sgornick) wrote :

Now with Feisty Herd-5, network-admin does replace the word "dhcp" with "static", so I suppose this bug is correct as having status "Fix Released".

However, I still cannot use network-admin to change my wired connection from dhcp to static. When I do that I get in my syslog:
  dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134993440

Bug #88101 addresses that problem.

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.