I was trying to track down why a machine was hanging at boot time. The hang appears to be caused by a bug in arping. The dhclient-script calls arping with arguments substantially similar to "arping -f -w 2 10.0.0.2", which should finish when a reply is received for 10.0.0.2 or within 2 seconds, whichever comes first. However, the following shows that arping seems to be ignoring the deadline option: root@prodigy# arping -f -I br0 10.0.0.34 ARPING 10.0.0.34 from 10.0.0.33 br0 Unicast reply from 10.0.0.34 [00:1F:D0:2E:2B:93] 0.635ms Sent 1 probes (1 broadcast(s)) Received 1 response(s) root@prodigy# time arping -f -I br0 10.0.0.2 ARPING 10.0.0.2 from 10.0.0.33 br0 ^C Sent 200 probes (200 broadcast(s)) Received 0 response(s) arping -f -I br0 10.0.0.2 0.00s user 0.01s system 0% cpu 3:19.36 total root@prodigy# I'm hoping that this should be enough information to reproduce the problem--it's certainly more helpful than a report that "my system hung at boot". :) Thanks.
iputils-20071127-10.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/iputils-20071127-10.fc13
iputils-20071127-10.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/iputils-20071127-10.fc12
iputils-20071127-10.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update iputils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/iputils-20071127-10.fc12
iputils-20071127-10.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
iputils-20071127-10.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.