static network settings not applied

Bug #173843 reported by M. O.
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Undecided
Pascal De Vuyst

Bug Description

I installed hardy alpha 1 on a empty partition,
and my network environment doesn't have a dhcp server.

I did set IPv4 IP, netmask, gateway and DNS manually in
the network settings GUI. However, after closing the
configuration application, the eth0 interface is not
setup with these settings.

I had to use ifconfig to setup IP and netmask on the
command line to get network working.

(I also added default gateway with route, however I
don't know if this was necessary or not)

Tags: hardy
Revision history for this message
Nanley Chery (nanoman) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.

Revision history for this message
Kow (kow) wrote :

I can confirm this bug using network-manager-0.6.5-0ubuntu17. Please see http://ubuntuforums.org/showthread.php?t=639256 for details.

Revision history for this message
Kow (kow) wrote :

Appears everyone is having these troubles in hardy at least since alpha 1.

Changed in network-manager:
status: New → Confirmed
Revision history for this message
chrismine (chrisjan-botha) wrote :

I have the same problem - running Hardy Alpha.

First a problem with network-admin not starting - now starting up but settings not kept. When I try to connect to my wireless network it keeps asking for the network key - when I checked the keyring it tells me the keyring daemon is not running. May this be related to Policykit?

Revision history for this message
Miguel Diago (mdm) wrote :

I can confirm this on Alpha 6 live CD.

In this case the only thing that is saved is the DNS addresses. I have then to set manually from console my IP and the gateway.

Revision history for this message
Miguel Diago (mdm) wrote :

Seems to be solved in Hardy Beta live CD.

Revision history for this message
MattW (seattle) (mbw) wrote :

Saw this behavior in the released Hardy Heron on i386 hardware on monday.

Solution after setting static ip info was to manually run:

/etc/init.d/networking restart

as root. Verified new address with:

ifconfig -a

Annoying, but will only need to do it once ever until reinstall

Matt

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Marcus,
This looks like a duplicate of bug 185854 which has already been fixed, is this still a problem for you?

Changed in network-manager:
assignee: nobody → pascal-devuyst
status: Confirmed → Incomplete
Revision history for this message
Saivann Carignan (oxmosys) wrote :

Static IPs are not managed by network-manager but network-admin, which is a part of gnome-system-tools. I reproduced this bug 2 hours ago and opened a bug in launchpad and bugzilla for gnome-system-tools. Therefore, I set this bug report as a duplicate of bug 246161 . Thanks for your contribution to ubuntu.

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.