Linux ip 隧道用了几天 ping 就变高了，但是直接 ping 没事，是主机商干的吗

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

现在注册

已注册用户请登录

这是一个创建于 1790 天前的主题，其中的信息可能已经有所发展或是发生改变。

PING 10.10.1.2 (10.10.1.2) 56(84) bytes of data.
64 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=78.7 ms
64 bytes from 10.10.1.2: icmp_seq=2 ttl=64 time=78.5 ms
64 bytes from 10.10.1.2: icmp_seq=3 ttl=64 time=78.5 ms

PING 103.52.153.169 (103.52.153.169) 56(84) bytes of data.
64 bytes from 103.52.153.169: icmp_seq=1 ttl=47 time=15.6 ms
64 bytes from 103.52.153.169: icmp_seq=2 ttl=47 time=15.4 ms
64 bytes from 103.52.153.169: icmp_seq=3 ttl=47 time=15.6 ms
64 bytes from 103.52.153.169: icmp_seq=4 ttl=47 time=15.5 ms

就 tm 离谱啊

ping

Linux

隧道

没事

13 条回复 • 2020-12-04 17:54:23 +08:00

CernetBoom

2020-11-30 20:53:37 +08:00 via Android

TCP/UDP 路由是不是变了

fvladlpa

2020-12-01 10:23:48 +08:00

很多主机商会优化 ICMP 的路由，看起来 ping 好看，不代表 TCP/UDP 走相同的路由，遇到这种商家还是绕路，选大厂把。

Overfill3641

2020-12-01 11:07:19 +08:00

@fvladlpa 这不叫优化，这叫骗

trepwq

2020-12-01 11:40:52 +08:00 via iPhone

qos 而已，非 tcp 的 qos 等级都很低

syjsq

2020-12-01 12:23:57 +08:00

[root@izwz9b1wnd8c5id7z4v1t3z bin]# tcping 154.209.73.217
traceroute to 154.209.73.217 (154.209.73.217), 255 hops max, 60 byte packets
seq 0: tcp response from 154.209.73.217 (154.209.73.217) <rst,ack> 77.762 ms
traceroute to 154.209.73.217 (154.209.73.217), 255 hops max, 60 byte packets
seq 1: tcp response from 154.209.73.217 (154.209.73.217) <rst,ack> 74.327 ms
traceroute to 154.209.73.217 (154.209.73.217), 255 hops max, 60 byte packets
seq 2: tcp response from 154.209.73.217 (154.209.73.217) <rst,ack> 71.420 ms
traceroute to 154.209.73.217 (154.209.73.217), 255 hops max, 60 byte packets
seq 3: tcp response from 154.209.73.217 (154.209.73.217) <rst,ack> 81.474 ms

我倒是不会看 tcp 路由，但是用 tcping 测了一下，主机商是真的狗啊，买的前两天正常，等不能退款了就给你改了。

我能爆出来这主机商吗！！