When compiled with dhclient use flag, it seems nm is passing the wrong arguments to dhclient or something. Which results in dhclient spitting out usage/help in logs, and failing to obtain an IP. If you switch to dhcpcd it works as expected, no problems obtaining and IP. I did not get a chance to dig into the sources to see exactly where the problem lies.
Please provide example output from logs and emerge --info..
Created attachment 290203 [details] emerge --info
Created attachment 290205 [details] nm dhclient log output
What version of net-misc/dhcp do you have installed? For reference, networkmanager-0.9.x's interface to dhclient is in src/dhcp-manager/nm-dhcp-dhclient.c in the networkmanager source. It calls dhclient -d [ -r ] [ -6 | -4 ] -sf $scriptpath -pf $pidpath -lf $leasepath -cf $confpath -e DBUS_SYSTEM_BUS_ADDRESS=blah As far as I can tell, all of those arguments should be supported by dhcp-4.2.3_p1's dhclient.
I tried using the latest in ~arch per the time of reporting this bug. I have since tried again and always run into the same issue. If you look at my attached log you can see that was with Oct 18 17:25:11 wlt dhclient: Internet Systems Consortium DHCP Client 4.2.2 Gentoo-r2 It should be easy to replicate, emerge the latest nm and dhclient, using that use flag not the dhcpcd one. Then try to get an IP via dhcp and you should see similar output in your logs as were in my attached logs. I can try it again, but I bet I will run into the same problem, unless its been fixed.
This is a duplicate of bug 335147. From your log..."Beginning DHCPv4 transaction" Networkmanager passes the '-6' and '-4' parameters to dhclient, but for these parameters to be available to dhclient, net-misc/dhcp *must* be built with 'ipv6' enabled, and so it fails. A patch for networkmanager is available on that bug.
(In reply to comment #6) > This is a duplicate of bug 335147. You are probably right. Should be fixed in networkmanager-0.9.4.0-r4 *** This bug has been marked as a duplicate of bug 335147 ***
