TFTP:等待来自192.168.1.100:69的数据包超时
TFTP: timeout waiting for data packet from 192.168.1.100:69
ID: networking/tftp-timeout-no-response
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| tftp-hpa 5.2 | active | — | — | — |
| Cisco IOS 15.9 | active | — | — | — |
| Linux tftp client 0.17 | active | — | — | — |
根因分析
TFTP客户端向服务器发送了读/写请求,但在超时时间内未收到数据包,通常由防火墙阻止UDP 69端口、文件路径错误或服务器过载引起。
English
A TFTP client sent a read/write request to the server but received no data packet within the timeout period, typically due to firewall blocking UDP port 69, incorrect file path, or server overload.
官方文档
https://linux.die.net/man/1/tftp解决方案
-
Check server connectivity with `tftp 192.168.1.100 -c get /path/to/file` and verify the server is running: `systemctl status tftpd-hpa`
-
Allow TFTP traffic through the firewall: `iptables -A INPUT -p udp --dport 69 -j ACCEPT` and ensure the TFTP server is not bound to localhost only.
-
Test with a known good file in the server's root directory (e.g., /srv/tftp) to rule out permission issues: `chmod 644 /srv/tftp/test.txt`
无效尝试
常见但无效的做法:
-
75% 失败
If the firewall is blocking the port or the file does not exist, no amount of waiting will help; the request will still fail after the extended timeout.
-
60% 失败
The client implementation is rarely the issue; the problem is almost always server-side or network-layer.
-
50% 失败
This is a security risk and may not solve the problem if the server's firewall is the blocker; also, it does not verify the server is running.