Red Hat Bugzilla – Bug 442257
Network partially started?
Last modified: 2009-02-20 11:02:04 EST
Description of problem:
Since Friday's update (11th Apr.) at bootup the network icon on the tray shows
no connection. ifconfig returns all that's expected. ping says 'Network is
unreachable. 'network-service-restart' shuts down, and bringing up eth0 causes
a longish delay, but after that everything works. The icon still says 'no
Version-Release number of selected component (if applicable):
Steps to Reproduce:
No network activity possible without restarting the network.
Network active from bootup.
The pause appears to be around 6 seconds.
I should have added that the network uses static IP.
What items are in the left-click dropdown menu of the NM applet?
What's the output of /usr/bin/nm-tool?
NM applet -
Enable Networking (checked)
Edit Connections (everything greyed out)
- Device: eth0 ----------------------------------------------------------------
HW Address: 00:00:00:00:00:00
Carrier Detect: yes
Speed: 100 Mb/s
The connection keeps dropping out, although it is active at the moment.
On starting the box this morning I discovered that it automatically connected.
This is the first time since the 11th. Maybe something changed in yesterday's
It will take a little time before I know whether it's totally stable, but it
seems to have only dropped out once in the last couple of hours, a definite
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Cabled connections appear to work normally now.
Possibly related -- I noticed that on FC8 as well as FC9, when a static IP is
specified during install, some network config is static, and some is DHCP even
though static is specified. Network does work (sort of) on reboot without
restarting network if DHCP server is configured to deliver same information as
specified for static IP.
I confirm that I did set the network to static during install.
Is this still an issue with latest NM and kernel updates?
I think it's safe to say that this is now fixed, thanks