networking
protocol_error
ai_generated
partial
PPPoE:LCP回显超时,未收到对端192.168.100.1的响应
PPPoE: LCP echo timeout, no response from peer 192.168.100.1
ID: networking/pppoe-lcp-echo-timeout
72%修复率
82%置信度
1证据数
2023-11-08首次发现
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| pppd 2.4.9 | active | — | — | — |
| pppd 2.5.1 | active | — | — | — |
| Linux kernel 5.10 | active | — | — | — |
根因分析
PPPoE会话的链路控制协议(LCP)回显请求未得到远程对端的确认,通常是由于接入集中器失效、DSL调制解调器故障或PPPoE服务器静默断开会话。
English
The PPPoE session's Link Control Protocol (LCP) echo requests are not being acknowledged by the remote peer, typically due to a dead access concentrator, a faulty DSL modem, or a misconfigured PPPoE server that has dropped the session silently.
官方文档
https://ppp.samba.org/pppd.html解决方案
-
killall pppd && pon dsl-provider
-
reboot modem via web interface or power cycle; then restart pppd: ifdown ppp0 && ifup ppp0
无效尝试
常见但无效的做法:
-
Setting lcp-echo-interval to a larger value (e.g., 60 seconds) to reduce timeout frequency.
80% 失败
This only delays the inevitable disconnection; the underlying peer unresponsiveness remains, and sessions still drop after the longer timeout.
-
Adding 'noecho' option to pppd to stop sending LCP echo requests.
95% 失败
Hides the failure but leaves the session in a broken state; the PPPoE connection may appear up but cannot pass traffic.