Bug 637929
Summary: | dhclient-script does "ip link set eth0 down" and after that dhclient fails with -ENETDOWN | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sami Farin <hvtaifwkbgefbaei> |
Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | jpopelka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-30 11:18:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sami Farin
2010-09-27 18:59:17 UTC
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 *** |