[network-admin] Static IP only apply after reboot.

Bug #246161 reported by Saivann Carignan
24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GST
Won't Fix
Medium
gnome-system-tools (Baltix)
Undecided
Unassigned
gnome-system-tools (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: gnome-system-tools

When configuring a network device with a static IP using network-admin, parameters are saved but not applied. In order to have static IP set, you have to reboot the computer or to type "sudo /etc/init.d/networking restart".

This is a bug because static IP should be applied automatically right after it has been configured in network-admin and it should not need to reboot or manual restart through terminal.

Steps to reproduce :
1. Have a connexion in Roaming mode, DHCP
2. Open network-admin
3. Configure the connexion to use static IP and close network-admin

Result :
The network is still not configured in static IP and you can't use the network at all unless you type "sudo /etc/init.d/networking restart" to apply the changes manually.

gnome-system-tools 2.22.0-0ubuntu5

Changed in gst:
status: Unknown → New
Revision history for this message
Saivann Carignan (oxmosys) wrote :

Confirmed by bug 173843

Changed in gnome-system-tools:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

Why importance of this bug is set to "Low" ? I think it's very important bug if user with static IP can't connect to network/internet !!!

Also I've noticed, that this bug is reproducible only if network manager process is running - static IP configuration is applied right after it has been configured in network-admin if I kill NetworkManager and NetworkManagerDispatcher before launching network-admin.

So, it seems this is not an upstream GST bug, but Ubuntu bug when using network-admin together with network-manager.

Changed in gst:
importance: Unknown → Medium
Revision history for this message
Lucas Campbell (lucas-campbell) wrote :

Confirming that I've been seeing this bug for a while when doing fresh installs, specifically for server. It's a pain when setting up a new server, as if you don't remember to restart the server after making the change, you'll typically end visiting the physical machine again to solve the problem within the next day.

Steps to reproduce:

1. Change /etc/network/interfaces file and set change interface from using 'dhcp' to 'static' and give appropriate information for the static connection.
2. Run /etc/init.d/networking restart, the IP will be set to the new static IP.
3. Wait. For me is usually takes a few hours, but inevitably the machine will grab an IP from DHCP and overwrite the statically set one.

If you run a /etc/init.d/networking restart it will set the static IP again, and repeat the process. Only upon a restart of the system will this problem stop occurring.

Changed in gst:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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