networking
network_error
ai_generated
partial
DHCPREQUEST timed out on interface eth0, waiting for DHCPOFFER
ID: networking/dhcp-request-timeout
80%Fix Rate
83%Confidence
1Evidence
2024-01-10First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| isc-dhcp-client 4.4.3 | active | — | — | — |
| dhcpcd 9.4.1 | active | — | — | — |
| NetworkManager 1.42 | active | — | — | — |
Root Cause
The DHCP client sent a DHCPREQUEST but did not receive a DHCPACK from the server within the timeout period, often due to server unavailability, network congestion, or VLAN misconfiguration.
generic中文
DHCP客户端发送了DHCPREQUEST,但在超时时间内未收到服务器的DHCPACK,通常是由于服务器不可用、网络拥塞或VLAN配置错误所致。
Official Documentation
https://www.isc.org/dhcp/Workarounds
-
90% success Check DHCP server connectivity: tcpdump -i eth0 port 67 or port 68 -vvv
Check DHCP server connectivity: tcpdump -i eth0 port 67 or port 68 -vvv
-
95% success Assign a static IP as a temporary fix: ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up
Assign a static IP as a temporary fix: ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up
中文步骤
Check DHCP server connectivity: tcpdump -i eth0 port 67 or port 68 -vvv
Assign a static IP as a temporary fix: ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up
Dead Ends
Common approaches that don't work:
-
80% fail
Increasing the DHCP timeout on the client only masks the problem if the server is unreachable due to firewall rules blocking UDP port 67/68.
-
70% fail
Restarting the network service repeatedly without checking the DHCP server logs can cause unnecessary downtime.