Bug 446527

Summary: no gateway route setup for network
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9CC: jmoskovc, madko, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-19 22:53:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/etc/sysconfig/network-scripts/ifcfg-eth0 from sys with no DNS
none
ifcfg-eth0 from fresh f9 install
none
/etc/sysconfig/network none

Description Tom Horsley 2008-05-14 22:53:26 UTC 
Description of problem:

When I installed fedora 9, I told it to initialize the network at boot
time with a static address and provided all the info including the
default gateway (a linksys router) at 192.168.1.1.

When the system boots, there is no gateway in the route tables.
After booting, if I manually type:

ip route add default via 192.168.1.1

then I can get to the outside world (before that only local devices
on the 192.168.1.0/24 lan were talking).

Version-Release number of selected component (if applicable):

This is whatever was shipped with the fedora 9 x86_64 DVD image,
and I doubt system-config-network is even the right component, but I
have no idea what other component to report.

How reproducible:

Every time I boot.

Steps to Reproduce:
1. see above
  
Actual results:

no default gateway

Expected results:

default gateway

Additional info:

If I bring up the properties for the eth0 device in the network
config app, the gateway field does indeed have 192.168.1.1
in it, but it doesn't seem to actually take effect when the system
boots. If I run nm-tool, it shows eth0 with a 0.0.0.0 gateway.
Comment 1 Tom Horsley 2008-05-15 01:41:12 UTC 
I just got the iproute-2.6.25-1.fc9.x86_64 update installed, and thought
that might have something to do with this bug, but when I rebooted,
I still had no route to my gateway :-(.
Comment 2 Tom Horsley 2008-05-15 12:35:59 UTC 
On my machine at work, I also don't get DNS info in resolv.conf, even though
I specified it at installation time the same way I did when installing at
home. Disabling the NetworkManager service and enabling network instead
fixes everything. Maybe anaconda should just do that when you specify a
static IP?
Comment 3 Dan Williams 2008-05-15 18:40:48 UTC 
Tom: installation with Anaconda within the past few weeks will write out the
correct DNS information to your ifcfg files, which will allow NetworkManager to
set up your DNS correctly.  NM handles static IPs and static DNS just fine as
long as anaconda writes out the stuff correctly.  I verified this yesterday with
a Fedora 9 Gold LiveCD install.

Could you attach your /etc/sysconfig/network-scripts/ifcfg-eth0 file so we can
see if it's set up correctly?
Comment 4 Tom Horsley 2008-05-15 20:06:05 UTC 
Created attachment 305533 [details]
/etc/sysconfig/network-scripts/ifcfg-eth0 from sys with no DNS

Here's the eth0 script from the system at work which had no DNS info.
I swear I put it in during install (which was using the i386 DVD image
from the official f9 release).

In fact, I must have put it in, because which I switched back to the
network script instead of NetworkManager, everything worked, so it did
have the info somewhere.
Comment 5 Edouard Bourguignon 2008-05-16 06:24:59 UTC 
Created attachment 305634 [details]
ifcfg-eth0 from fresh f9 install

here is my ifcfg-eth0, static network configuration during install, and now no
default route on boot. Fix in Bug #446428 resolves the problem
Comment 6 Edouard Bourguignon 2008-05-16 06:28:35 UTC 
mmm no doesn't really fix the problem, sorry, the network connection is messy,
some apps (firefox, packagekit) think the computer is offline. So i remove the
ifcfg-eth0 and now NetworkManager find the link and network is fine (not static
as i wish but I can wait till it get fixed)
Comment 7 Dan Williams 2008-05-19 16:57:42 UTC 
I think the issue is a missing gateway in the ifcfg file, which is probably in
/etc/sysconfig/network actually.  I'll push an update to pull info from that
file if the ifcfg file doesn't have it.

Can you attach your /etc/sysconfig/network file?
Comment 8 Tom Horsley 2008-05-19 17:42:04 UTC 
Created attachment 305986 [details]
/etc/sysconfig/network

Here's the network file. I'm pretty sure it has all the info correct
since everything worked fine once I disabled NetworkManager and enabled
network.
Comment 9 Dan Williams 2008-05-19 18:46:59 UTC 
Thanks; that's what I need.  Will be fixed in an update for F9; already fixed in
rawhide with svn3675 and later.
Comment 10 Dan Williams 2008-05-19 19:38:05 UTC 
When they finish, can you try:

http://koji.fedoraproject.org/koji/taskinfo?taskID=618281

thanks!
Comment 11 Dan Williams 2008-05-19 19:38:46 UTC 
Of course you'll want to:

/sbin/chkconfig NetworkManager on
/sbin/chkconfig network off
service NetworkManager start

after installing the new packages.
Comment 12 Tom Horsley 2008-05-19 22:02:34 UTC 
Hey, it worked! I installed the x86_64 packages from comment #10 above,
disabled network, enabled NetworkManager, and rebooted, and my network
was functional. Didn't have to add the gateway by hand.

Of course, now I've added bug 447442 :-).
Comment 13 Dan Williams 2008-05-19 22:53:17 UTC 
Awesome, closing this one then.  Thanks!
Comment 14 Fedora Update System 2008-05-22 16:12:09 UTC 
NetworkManager-0.7.0-0.9.3.svn3675.fc9 has been submitted as an update for Fedora 9