Bug 588922 - NetworkManager-0.8.0-11.git20100503.fc12 fails to get DHCP lease
Summary: NetworkManager-0.8.0-11.git20100503.fc12 fails to get DHCP lease
Keywords:
Status: CLOSED DUPLICATE of bug 588814
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
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: 2010-05-04 20:10 UTC by Thomas Meyer
Modified: 2010-05-04 21:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-04 21:49:54 UTC
Type: ---


Attachments (Terms of Use)

Description Thomas Meyer 2010-05-04 20:10:01 UTC
Description of problem:

After upgrading to latest version of NetworkManager,  the software fails to get a DHCP lease. See log file (/var/log/messages):

May  4 21:56:25 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto WeyerS' has security, but secrets are requ
ired.
May  4 21:56:25 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0)
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May  4 21:56:25 localhost NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0)
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May  4 21:56:25 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto WeyerS' has security, and secrets exist.  No
 new secrets needed.
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'ssid' value 'WeyerS'
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1'
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
May  4 21:56:25 localhost NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
May  4 21:56:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  4 21:56:25 localhost NetworkManager: <info> Config: set interface ap_scan to 1
May  4 21:56:25 localhost NetworkManager: <info> (wlan0): supplicant connection state:  disconnected -> associating
May  4 21:56:27 localhost kernel: wlan0: media connect
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): supplicant connection state:  associating -> associated
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): supplicant connection state:  associated -> completed
May  4 21:56:27 localhost NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WeyerS'.
May  4 21:56:27 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May  4 21:56:27 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0)
May  4 21:56:27 localhost NetworkManager: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May  4 21:56:27 localhost NetworkManager: <info> dhclient started with pid 17053
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): device state change: 7 -> 9 (reason 0)
May  4 21:56:27 localhost NetworkManager: <warn> Activation (wlan0) failed for access point (WeyerS)
May  4 21:56:27 localhost NetworkManager: <info> Marking connection 'Auto WeyerS' invalid.
May  4 21:56:27 localhost NetworkManager: <warn> Activation (wlan0) failed.
May  4 21:56:27 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0)
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): deactivating device (reason: 0).
May  4 21:56:27 localhost NetworkManager: <info> (wlan0): canceled DHCP transaction, DHCP client pid 17053
May  4 21:56:27 localhost kernel: wlan0: media disconnect
May  4 21:56:58 localhost NetworkManager: <info> caught signal 15, shutting down normally.
May  4 21:56:58 localhost NetworkManager: <info> (eth0): cleaning up...
May  4 21:56:58 localhost NetworkManager: <info> (eth0): taking down device.
May  4 21:56:58 localhost NetworkManager: <info> (eth1): cleaning up...
May  4 21:56:58 localhost NetworkManager: <info> (eth1): taking down device.
May  4 21:56:58 localhost NetworkManager: <info> (wlan0): taking down device.


Version-Release number of selected component (if applicable):
NetworkManager-0.8.0-11.git20100503.fc12

How reproducible:
Choose the correct wireless network in gnome component and see the try-to-connect-circle spinning and immediately switch back to the not-connected symbol. 

Steps to Reproduce:
1.
2.
3.
  
Actual results:
No IP address is assigned to the network device

Expected results:
IP adress should be assigned

Additional info:

Comment 1 Dan Williams 2010-05-04 21:49:54 UTC

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


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