After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 501344 - Static IP specified but dynamic used and not setting up network correctly
Static IP specified but dynamic used and not setting up network correctly
Status: RESOLVED DUPLICATE of bug 359600
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-12-03 20:04 UTC by Scott Brown
Modified: 2008-01-24 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott Brown 2007-12-03 20:04:51 UTC
Please describe the problem:
In Fedora 8 live setup I specify a static IP address, with gateway, DNS servers etc.  and no IPV6.  On start up I get a DHCP address with an empty resolv.conf and no gateway in the routing table...  Checking the /etc/sysconfig/network* files they seem to be all correct.  Using the System->Administration->Network tool I can get the network to go by adding the DNS entries

Steps to reproduce:
1. Insert Fedora8 Live CD and boot
2. Install Fedora8 with static IP address, gateway address, DNS and turn off IPV6
3. Also, only localhost is used for computer hostname, domain or other info.
4. On system boot the NetworkManager starts and takes a good while to come back with a DHCP address, no DNS entries in resolv.conf, no gateway in the routing tables.


Actual results:


Expected results:
I'd expect to have what I get when I run "ifconfig eth0 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx up" "route add default gw xxx.xxx.xxx.xxx" and add the DNS addresses in /etc/resolv.conf, a working network...

Does this happen every time?
Yes, done it twice on two different machines.

Other information:
Adding the DNS entries etc. does not solve the problem.  I have to manually fix it each time I boot the system.
Comment 1 Dan Williams 2008-01-24 19:24:47 UTC

*** This bug has been marked as a duplicate of 359600 ***