Dhcpcd and/or dhclient must be explicitly enabled/disabled using the new configure options --with-dhclient=[yes|no] --with-dhcpcd=[yes|no] otherwise ./configure will use auto-magic.
version networkmanager-0.8.1-r2 should fix all the issues. Closing this bug now. If you still see this problem, please re-open.
How can I fix it using dhclient? /usr/sbin/NetworkManager --no-daemon NetworkManager[26316]: <info> Activation (wlan0) starting connection 'Auto NETGEAR007' NetworkManager[26316]: <info> (wlan0): device state change: 3 -> 4 (reason 0) NetworkManager[26316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager[26316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager[26316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager[26316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager[26316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager[26316]: <info> (wlan0): device state change: 4 -> 5 (reason 0) NetworkManager[26316]: <info> Activation (wlan0/wireless): connection 'Auto NETGEAR007' requires no security. No secrets needed. NetworkManager[26316]: <info> Config: added 'ssid' value 'NETGEAR007' NetworkManager[26316]: <info> Config: added 'scan_ssid' value '1' NetworkManager[26316]: <info> Config: added 'key_mgmt' value 'NONE' NetworkManager[26316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager[26316]: <info> Config: set interface ap_scan to 1 NetworkManager[26316]: <info> (wlan0): supplicant connection state: disconnected -> scanning NetworkManager[26316]: <info> (wlan0): supplicant connection state: scanning -> associating NetworkManager[26316]: <info> (wlan0): supplicant connection state: associating -> associated NetworkManager[26316]: <info> (wlan0): supplicant connection state: associated -> completed NetworkManager[26316]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'NETGEAR007'. NetworkManager[26316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager[26316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... NetworkManager[26316]: <info> (wlan0): device state change: 5 -> 7 (reason 0) NetworkManager[26316]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) NetworkManager[26316]: <info> dhclient started with pid 26448 NetworkManager[26316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client V3.1.2p1-Gentoo Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server] [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val] [-sf script-file] [interface] If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting. NetworkManager[26316]: <info> (wlan0): DHCPv4 client pid 26448 exited with status 1 NetworkManager[26316]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled... NetworkManager[26316]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started... NetworkManager[26316]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager[26316]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete. NetworkManager[26316]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... NetworkManager[26316]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found) NetworkManager[26316]: <info> (wlan0): device state change: 7 -> 9 (reason 5) NetworkManager[26316]: <warn> Activation (wlan0) failed for access point (NETGEAR007) NetworkManager[26316]: <info> Marking connection 'Auto NETGEAR007' invalid. NetworkManager[26316]: <warn> Activation (wlan0) failed. NetworkManager[26316]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. NetworkManager[26316]: <info> (wlan0): device state change: 9 -> 3 (reason 0) NetworkManager[26316]: <info> (wlan0): deactivating device (reason: 0). (In reply to comment #1) > version networkmanager-0.8.1-r2 should fix all the issues. > > Closing this bug now. If you still see this problem, please re-open. >
Re-opening as still seeing the problem in -r3.
(In reply to comment #3) > Re-opening as still seeing the problem in -r3. > hi, after refering to bug 330319, I upgraded to =net-misc/dhcp-4.1.0, and this solved my problem. So, as the Comment #3 in bug 330319 says, This seems to be a dependency of Networkmanager-0.8.1 to dhcp-4.x (because of some parameters) (when you have dhclient as use flag) Unmasking and emerging dhcp-4.1.0 allows you to get an IP.
(In reply to comment #3) > Re-opening as still seeing the problem in -r3. > Hi Rick, Can you please let me know how do you reproduce this problem? Right now NM should work with either DHclient 3 or 4 and dhcpcd.
I've pushed another revision to portage tree. Networkmanager-0.8.1-r6 should hopefully fix all dhcpcd/dhclient{3,4} problems we had. Please test and let me know. If you can still see the problems, please re-open this bug.
(In reply to comment #5) > Hi Rick, > > Can you please let me know how do you reproduce this problem? > > Right now NM should work with either DHclient 3 or 4 and dhcpcd. > To reproduce I had both dhcpcd and dhclient installed, then set '+dhclient -dhcpcd' USE flags for networkmanager. But it matters not as -r6 resolves the issue now, thanks for fixing :)
(In reply to comment #6) > I've pushed another revision to portage tree. Networkmanager-0.8.1-r6 should > hopefully fix all dhcpcd/dhclient{3,4} problems we had. Please test and let me > know. > > If you can still see the problems, please re-open this bug. > thank you for fixing this bug in Networkmanager-0.8.1-r6
