大网数据广告活动
服务器运维问答

ping fails with MTU >= 298

· 52CE 我爱测

For context, my original problem is that my ssh connection to my servers hangs at expecting SSH2_MSG_KEX_ECDH_REPLY when i connect to them via VPN (in this case, an OpenVPN running in pfsense). The Internet indicates that may be …

问题原文

原帖链接 · iCart · CC BY-SA 3.0

For context, my original problem is that my ssh connection to my servers hangs at expecting SSH2_MSG_KEX_ECDH_REPLY when i connect to them via VPN (in this case, an OpenVPN running in pfsense).

The Internet indicates that may be linked to MTU issues.

While trying to debug this, this happened:

ping -s 297 -M do $HOST

works fine, but

ping -s 298 -M do $HOST

just hangs.

The MTU is set to 1500 on both my machine, the host, and the pfsense interface (although the interface is disabled in pfsense's UI, i'm not sure if it's supposed to be that way).

Why is that happening? Is something blocking packets too large? Where could i even dig for more clues?

mtr $HOST indicates two hops: to the pfsense, then to the server itself

已采纳解答

原帖链接 · kostix · CC BY-SA 3.0

The fact you have set MTU on the hosts you control means nothing as the packets between them — in theory — might fly through any media with any MTU.

To deal with this issue (besides the IP fragmentation mechanism), the so-called "Path MTU discovery" mechanism exists.

Note that it relies on the ICMP protocol to work properly. Beside other things, it means that if you have tight firewall settings, you must have something like

iptables -t nat -A $CHAIN -m state --state RELATED -j ACCEPT

in your rules for your INPUT chain (and in the FORWARD chain if your firewall also does SNAT for its clients).

The "related" state means that when an ICMP packet of the type 3, code 4 (destination unreachable / fragmentation required) is received, the conntrack subsystem decides which connection it is related to and then passes it further down the netfilter stack. The state of such packet is "RELATED" as known to iptables¹ so if you have passing of such packets denied — as often happens when people disable everything wholesale and then punch the minimal holes — P-MTU discovery won't work properly.

Note also that even if you "unbreak" proper support for P-MTU on your sides, it might still be broken somewhere in between.

In order to deal with it, there exists at least two knobs:

  • Clamping MSS to MTU in the IP stack.
  • Limiting these things on the OpenVPN level by its tun-mtu, tun-mtu-extra and mssfix knobs.

Note that these settings does affect performance, so use as the last resort.


¹ Because while not a part of an IP exchange, it's clearly related to it.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-10-31)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。