Bug 507456 - NetworkManager won't connect to Wired Network
Summary: NetworkManager won't connect to Wired Network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 11
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-22 20:17 UTC by jameswithers89
Modified: 2009-11-12 01:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-12 01:11:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jameswithers89 2009-06-22 20:17:25 UTC
Description of problem: NetworkManager times out when trying to get its IP address (DHCP) from a Belkin G+ MIMO Router.

Version-Release number of selected component (if applicable): NetworkManager-0.7.1-4.git20090414.fc11.x86_64. Wired Network Hardware: Broadcom NetXtreme BCM5754 Gigabit Ethernet PCI Express.

How reproducible: happens everytime I try 'Wired Network'. Wireless Network works with no problems (Realtek RTL-8185).

Steps to Reproduce:
1. Click on NetworkManager (on Gnome panel).
2. Click on 'System eth0' (under 'Wired Network').
  
Actual results: (from /var/log/messages)

Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) starting connection 'System eth0'
Jun 22 20:55:05 localhost NetworkManager: <info>  (eth0): device state change: 3 -> 4
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 22 20:55:05 localhost NetworkManager: <info>  (eth0): device state change: 4 -> 5
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 22 20:55:05 localhost NetworkManager: <info>  (eth0): device state change: 5 -> 7
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Jun 22 20:55:05 localhost dhclient: Internet Systems Consortium DHCP Client 4.1.0
Jun 22 20:55:05 localhost dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jun 22 20:55:05 localhost dhclient: All rights reserved.
Jun 22 20:55:05 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jun 22 20:55:05 localhost dhclient: 
Jun 22 20:55:05 localhost NetworkManager: <info>  dhclient started with pid 3682
Jun 22 20:55:05 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 22 20:55:05 localhost NetworkManager: <info>  DHCP: device eth0 state changed (null) -> preinit
Jun 22 20:55:05 localhost dhclient: Listening on LPF/eth0/00:1a:a0:df:9b:eb
Jun 22 20:55:05 localhost dhclient: Sending on   LPF/eth0/00:1a:a0:df:9b:eb
Jun 22 20:55:05 localhost dhclient: Sending on   Socket/fallback
Jun 22 20:55:06 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 22 20:55:09 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Jun 22 20:55:15 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 22 20:55:27 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Jun 22 20:55:48 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Jun 22 20:55:50 localhost NetworkManager: <info>  Device 'eth0' DHCP transaction took too long (>45s), stopping it.
Jun 22 20:55:50 localhost NetworkManager: <info>  eth0: canceled DHCP transaction, dhcp client pid 3682
Jun 22 20:55:50 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jun 22 20:55:50 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
Jun 22 20:55:50 localhost NetworkManager: <info>  (eth0): device state change: 7 -> 9
Jun 22 20:55:50 localhost NetworkManager: <info>  Marking connection 'System eth0' invalid.
Jun 22 20:55:50 localhost NetworkManager: <info>  Activation (eth0) failed.
Jun 22 20:55:50 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Jun 22 20:55:50 localhost NetworkManager: <info>  (eth0): device state change: 9 -> 3
Jun 22 20:55:50 localhost NetworkManager: <info>  (eth0): deactivating device (reason: 0).
Jun 22 20:55:50 localhost NetworkManager: <info>  Policy set 'Auto Belkin_G' (wlan0) as default for routing and DNS.

Expected results: a 'Wired Network' connection.

NetworkManager 'Wired Network' worked fine when I used it to install and update Fedora 11 a few days after it was released.

Comment 1 Joel Uckelman 2009-08-11 21:25:50 UTC
I'm having precisely the same problem with a ZyXEL P-2602HW-D1A router and an Intel PRO/1000 NIC in my ThinkPad T61.

NetworkManager-0.7.1-8.git20090708.fc11.x86_64

Similarly for me, there was no problem with eth0 when I installed F11---it stopped working sometime after the initial install.

Comment 2 Joel Uckelman 2009-08-12 09:16:54 UTC
The problem went away for me after applying yesterday's updates and rebooting. Weird.

Comment 3 Dan Williams 2009-11-12 01:11:08 UTC
Ok, thanks for updating with the new information.  Weird.  Bug #507351 seems to be the same problem, but with sky2 instead of b44 or e1000.


Note You need to log in before you can comment on or make changes to this bug.