Created attachment 938504 [details] lshw from a Fedora 21 install with fixed ip Description of problem: During an installation with RC1, the Ethernet is never enabled because there is a DHCP timeout. This is a physical machine (Dell Optiplex 755). DHCP works consistently with Fedora 20. Version-Release number of selected component (if applicable): 21 RC1 How reproducible: always Steps to Reproduce: 1.Boot from USB key 2. 3. Actual results: Ethernet is assigned only 127.0.0.1 Expected results: Ethernet is assigned ip address from DHCP server Additional info: Attaching an lshw output for machine
This issue does not appear when using a KVM virtual machine, so I suspect that the problem may actually be in the hardware driver.
The problem still exists in F21 Alpha. I wonder if this is related to https://bugzilla.redhat.com/show_bug.cgi?id=560361 When I create a /etc/dhcp/dhclient.conf containing send dhcp-client-identifier = hardware; the DHCP request succeeds.
My colleague suggests that my problem has been caused by patch29 (duidv4) which has enabled the sending of the DUID.
The problem still exists in F21 Beta TC1. The solution in #2 still works.
As I understand it, the problem seems to be with handling DHCP client identifier. dhclient bugs: https://bugzilla.redhat.com/show_bug.cgi?id=560361#c44 https://bugzilla.redhat.com/show_bug.cgi?id=1109860 From NetworkManager side the client identifier can be controlled by ipv4.dhcp-client-id property, which is DHCP_CLIENT_ID variable in ifcfg files. Can you get messages logs so that we can see what is sent to DHCP server and what's the reply?
Created attachment 943349 [details] /tmp/syslog after initial DHCP timeout
Created attachment 943351 [details] /tmp/syslog after dhclient.conf file added
Yes, you're right. Your BZ 1109860 seems to be concerned with IP over IB and, while I do use that as well, this is just a straight-up Ethernet that is not working. That /etc/dhcp/dhclient.conf file was provided by the dhclient rpm in Fedora 20. That's why I've continued adding it. NetworkManager seems to merge it into the ifcfg file that it creates. I've provided what I believe are the logs you need. It's easy to reproduce if there are are others need.
The problem still exists in F21 Beta TC2. The solution in #2 still works.
The problem still exists in F21 Server (and Workstation) Beta TC3. The solution in #2 still works.
This appears to be a side effect of our local DHCP server's restrictions rather than a general problem. I have tried F21 Server Beta TC4 in several other (DHCP) contexts without problems. Closing the ticket.
please can this be reopened. I've just ran into it in fedora 21 final workstation on multiple machines. the proposed fixed in #2 worked.
Yup. Same problem here. Strange!
I'm fine with reopening it. I don't know the protocols for doing so. Rob and Richard Guest: do you know how your dhcp server is responding to the sending of the duid instead of the (old) hardware id? Mine (a 1998 vintage) just completely ignores the request, hence the timeout.
It's a windows dhcp server, and i see no reply on wireshark/tcpdump at the client at all, so i guess it's also completely ignoring the request.