Description of problem: Sep 21 16:07:14 safari dhclient[9612]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 37 Sep 21 16:07:14 safari dhclient[9612]: send_packet: Network is down Sep 27 15:25:56 safari dhclient[29077]: No working leases in persistent database - sleeping. Sep 27 15:26:01 safari dhclient[29077]: receive_packet failed on eth0: Network is down script should be a teeny bit smarter in handling cases EXPIRE|FAIL|RELEASE|STOP and TIMEOUT Version-Release number of selected component (if applicable): 4.2.0-7 How reproducible: always Steps to Reproduce: 1. start dhclient 2. fail to get IP address from DHCP server on first try 3. Actual results: link stays down Expected results: dhclient manages to send something Additional info:
Seems similar to bug #574568. But I'm not able to reproduce that (maybe it's hardware related problem). Can you better describe the steps to reproduce ? Is this (4.2.0-7.fc14) the first time you see this problem ? DHCP servers, relays, and clients all should be able to transmit and receive a UDP packet on an unconfigured interface (in order to speak the DHCP protocol in strict compliance with RFC2131). So bringing the interface down shouldn't be a problem.
did you get to step 2 ? you should have "${reason}" TIMEOUT or FAIL. I have also PERSISTENT_DHCLIENT=yes and I have also ONBOOT=no or otherwise bootup stalls for some minutes when network is not working during boot. "unconfigured interface" is not the same as "interface down". when interface is down, you get write(5, "...", 342) = -ENETDOWN (Network is down)
(In reply to comment #2) > "unconfigured interface" is not the same as "interface down". > when interface is down, you get > write(5, "...", 342) = -ENETDOWN (Network is down) You are right. *** This bug has been marked as a duplicate of bug 574568 ***