[network-admin] Static IP configuration doesn't adds the default route to the gateway

Bug #59690 reported by Rui Ferreira
108
Affects Status Importance Assigned to Milestone
GST
Fix Released
Medium
gnome-system-tools (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

http://www.ubuntuforums.org/showthread.php?t=252944&page=2

How to reproduce:

- Go to System, Administration, Networking
- Select wired connection
- Change Configuration to: Static IP address
- Configure your IP, Mask and gateway
- Open a shell and type route

Result:
- No default route exists
- The gateway is not saved in the form

Revision history for this message
Travis Watkins (amaranth) wrote : Re: Static IP configuration doesn't adds the default root to the gateway

Reassigning to gnome-system-tools - this bug is for network-admin, not network-manager.

Revision history for this message
Florent Mertens (givre) wrote :

Little comment.
Changing gatway in network-admin seems to not affect
/etc/network/interfaces.
adress & netmask seems to work, but not gatway.

Step to reproduce :
- enter a gatway & an adress for an interface in network-admin
- close it
- check /etc/network/interfaces. adress is there but not gatway.
- reopen network-manager, adress is ok, but gatway is left blank.

Revision history for this message
Florent Mertens (givre) wrote :

Can't affect network-manager since it don't support at all static IP.
This bug is only for network-admi.
rejected

Changed in network-manager:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: Static IP configuration doesn't adds the default route to the gateway

Thanks for your bug. I've forwarded it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=355509

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
importance: Untriaged → High
status: Unconfirmed → Confirmed
Changed in gst:
status: Unknown → Unconfirmed
Revision history for this message
Francesco Fumanti (frafu) wrote :

I have the same problem with knot 3 of edgy i386: it does not save the gateway address when using the Networking pane.

Workaround that seems to work for me: Close the Networking pane and don't open it anymore. Then add the following line to the corresponding interface in the file /etc/network/interfaces

[code]
gateway xxx.xxx.xxx.xxx
[/code]

Of course, xxx.xxx.xxx.xxx has to be the address of the gateway.

Revision history for this message
Francesco Fumanti (frafu) wrote :

I forgot to mention to restart the computer.

Revision history for this message
Soroosh Radpoor (ssh-rdp) wrote :

It seems there is fixme related to this problem in liboobs-1-1 source in src/oobs-ifacesconfig.c line 416:
  if (OOBS_IS_IFACE_ETHERNET (iface))
    {
      gchar *address, *netmask;
      gint config_method;
      g_object_get (G_OBJECT (iface),
      "ip-address", &address,
      "ip-mask", &netmask,
      "config-method", &config_method,
      NULL);
      /* FIXME: can pass config_method like that? */
      dbus_message_iter_append_basic (&iter, DBUS_TYPE_INT32, &config_method);
      utils_append_string (&iter, (configured) ? address : NULL);
      utils_append_string (&iter, (configured) ? netmask : NULL);
printf("%s\n",address);
printf("%s\n",gateway);
      /* FIXME */

      utils_append_string (&iter, (configured) ? gateway : NULL);
      utils_append_string (&iter, (configured) ? gateway : NULL);

      /* FIXME: missing gateway and possibly other stuff */

Revision history for this message
Yves Dessertine (yvesd) wrote :

Confirmed using Beta Live CD.

Workaround for the session was a :
sudo route add default gw 192.168.0.1

This is the only bug I found yet in this beautiful LiveCD (but an annoying bug...)

Revision history for this message
Tom R (asub) wrote :

Also apparent once Edgy beta had been installed from the desktop CD.

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

Those uploads fix the issue:

 system-tools-backends (1.9.7-0ubuntu1) edgy; urgency=low
 .
   * New upstream version:
     - Fix SMBConfig not recognizing share names with spaces in it
     - SunOS (OpenSolaris and Nexenta) support for all modules
     - Get/set gateway settings properly in static interfaces (Ubuntu: #59690)
   * debian/patches/90_from_cvs_fix_parsing_issue.patch:
     - fixed with the new version

 liboobs (0.6.0-0ubuntu1) edgy; urgency=low
 .
   * New upstream version:
     - Handle better the situations where Liboobs can't get a DBusConnection
     - Fix supported platforms retrieving
     - Get/set the gateway properly for static interfaces (Ubuntu: #59690)
     - Code robustness improvements
   * debian/control:
     - require new system-tools-backend version
   * debian/patches/90_from_cvs_no_assert_when_dbus_not_running.patch:
     - fixed with the new version
   * debian/patches/91_from_cvs_dont_crash_on_configuration_issue.patch:
     - fixed with the new version

Changed in gnome-system-tools:
status: Confirmed → Fix Released
Revision history for this message
Stéphane Démurget (stephane-demurget-free) wrote :

I also got the issue on my edgy installation and now the problem seems to be fixed but introduced a regression. If I only change the gateway on my wireless connection (eth1) to 192.168.0.200, it is correctly changed in my /etc/network/interfaces file, but I've got no more WiFi connectivity because two fields are overwritten. I get :

wireless-essid 192.168.0.200
wireless-key s:1

I'm used to have a correct network name "ubuntu" and an hexa key.

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

Stéphane, thank you for pointing that regression. Could you open a different bug about it though? It would make work much easier for everybody than abusing a fixed issue. Feel free to mention on the new bug that it happens after the fix of that one

Revision history for this message
Stéphane Démurget (stephane-demurget-free) wrote :

done as #64719, thanks.

Changed in gst:
status: Unconfirmed → Fix Released
Changed in gst:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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