Fedora Account System
Red Hat Associate
Red Hat Customer
After upgrading this morning to dhclient-4.2.4-1.P2.fc16 and rebooting, dhclient obtained and logged to /var/log/messages an IP address for eth0 but didn't configure the address onto the device. I had to do "ifconfig eth0 <addr> netmask 255.255.0.0" and then "route add default dev eth0 gw <gateway-from-leases-file>" to get my network up and running. Downgrading to the older dhclient, dhcp-libs and dhcp-client fixes the problem. I have SELinux enabled, but there's nothing in /var/log/audit/audit.log to suggest an SELinux issue.
Whoops !
dhcp-4.2.4-3.P2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dhcp-4.2.4-3.P2.fc16
Jonathan, can you try these builds http://koji.fedoraproject.org/koji/buildinfo?buildID=357937 and leave a karma at https://admin.fedoraproject.org/updates/dhcp-4.2.4-3.P2.fc16 Thanks
It looks like /sbin/dhclient hardcoded to execve /usr/sbin/dhclient-script, while the script is actually in /sbin/dhclient-script. A sym-link to the actual file fixed my fc16. /var/log/messages: >Oct 3 04:57:55 localhost dhclient[1152]: execve (/usr/sbin/dhclient-script, ...): No such file or directory >Oct 3 04:57:55 localhost dhclient[1151]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 >Oct 3 04:57:55 localhost dhclient[1151]: DHCPACK from 192.168.1.1 >Oct 3 04:57:55 localhost dhclient[1153]: execve (/usr/sbin/dhclient-script, ...): No such file or directory >Oct 3 04:57:55 localhost dhclient[1151]: bound to 192.168.1.123 -- renewal in 37016 seconds.
seeing the same issue on my fedora 16 client. hitting the problem with linked to /usr/sbin/dhclient-script as chris chen indicated above.
https://admin.fedoraproject.org/updates/dhcp-4.2.4-3.P2.fc16 has been in stable since 2012-10-04