通过路由器连接互联网时，我的 ping 时间比没有路由器时慢 2-5 倍。波动可能非常短，如 delta 函数，也可能非常长，如呼吸波。我住在一个很大的学生宿舍里，所以其他学生可能会发生重大的下载过程，但我仍然对如此大规模的时间事件感到惊讶，因为在这里住了两年，这种事情从未发生过。直接从墙上上网要快得多。我检查了路由器的所有设置，但找不到任何解释。已完成的事情
- 我切换了所有电缆，因此个别电缆应该不会有问题。
- 我大大缩短了网络中的 RJ45 电缆，以尽量减少电缆损坏或尽量减少 RJ45 电缆总距离对网络速度的影响。
- 我关闭了 2.5 GHz wifi 频道，现在只使用 5 GHz。它平均将到达 Google 的最短时间从 4 毫秒缩短到了 2 毫秒。
- 我将网络中的电缆数量减少了一半。
其他答案
- 使用有线路由器和使用 wifi 之间的性能没有变化。
- 我已经在 7 个不同的系统上进行了测试。
- 我已经禁用 V6 的所有部分，仅禁用 V4。
- 我正在使用正在变化的 ISP 的 IP 地址。
- 同一走廊的其他一些学生也遇到了同样的 ping 问题。这个问题从昨天开始，一直持续到现在。
不使用路由器时的 ping 时间示例
PING google.com (159....) 56(84) bytes of data.
64 bytes from cache.google.com (159....): icmp_seq=1 ttl=58 time=2.20 ms
64 bytes from cache.google.com (159....): icmp_seq=2 ttl=58 time=1.85 ms
64 bytes from cache.google.com (159....): icmp_seq=3 ttl=58 time=2.10 ms
64 bytes from cache.google.com (159...): icmp_seq=4 ttl=58 time=2.49 ms
...
无需路由器的 Traceroute
root@masi:/etc/openvpn# tracepath google.com
1?: [LOCALHOST] pmtu 1500
1: 10.10.10.1 0.936ms
1: 10.10.10.1 0.751ms
2: 83.241.95.1 1.986ms
3: vl548-opt.sw4.riga2.nano.lv 1.846ms
4: 91.203.69.93 2.130ms
5: 159.148.79.58 1.812ms
6: titan-gw.v3000.latnetserviss.lv 2.636ms
7: no reply
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
路由器的短暂波动
masi@masi:~$ ping google.com
PING google.com (159....) 56(84) bytes of data.
64 bytes from cache.google.com (159...): icmp_seq=1 ttl=57 time=1159 ms
64 bytes from cache.google.com (159...): icmp_seq=2 ttl=57 time=168 ms
64 bytes from cache.google.com (159...): icmp_seq=3 ttl=57 time=1187 ms
64 bytes from cache.google.com (159...): icmp_seq=4 ttl=57 time=196 ms
64 bytes from cache.google.com (159...): icmp_seq=5 ttl=57 time=1711 ms
64 bytes from cache.google.com (159...): icmp_seq=6 ttl=57 time=710 ms
64 bytes from cache.google.com (159...): icmp_seq=7 ttl=57 time=1666 ms
64 bytes from cache.google.com (159...): icmp_seq=8 ttl=57 time=666 ms
64 bytes from cache.google.com (159...): icmp_seq=9 ttl=57 time=2765 ms
64 bytes from cache.google.com (159...): icmp_seq=10 ttl=57 time=1766 ms
64 bytes from cache.google.com (159...): icmp_seq=11 ttl=57 time=766 ms
64 bytes from cache.google.com (159...): icmp_seq=12 ttl=57 time=1578 ms
64 bytes from cache.google.com (159...): icmp_seq=13 ttl=57 time=578 ms
--- google.com ping statistics ---
17 packets transmitted, 15 received, 11% packet loss, time 18711ms
rtt min/avg/max/mdev = 168.450/1140.935/2765.809/684.821 ms, pipe 3
使用路由器跟踪路由
root@masi:/etc/openvpn# tracepath google.com
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 5.763ms
1: 192.168.1.1 2.984ms
2: 10.10.10.1 15.920ms
3: 83.241.95.1 21.458ms
4: vl548-opt.sw4.riga2.nano.lv 256.015ms
5: 91.203.69.93 251.707ms
6: 159.148.79.58 84.024ms
7: titan-gw.v3000.latnetserviss.lv 8.012ms
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
路由器长时间波动
bytes from cache.google.com (159....): icmp_seq=6 ttl=57 time=3.76 ms
64 bytes from cache.google.com (159....): icmp_seq=7 ttl=57 time=5.78 ms
64 bytes from cache.google.com (159...): icmp_seq=8 ttl=57 time=7.70 ms
64 bytes from cache.google.com (159...): icmp_seq=9 ttl=57 time=5.40 ms
64 bytes from cache.google.com (159....): icmp_seq=10 ttl=57 time=8.10 ms
64 bytes from cache.google.com (159....): icmp_seq=11 ttl=57 time=6.99 ms
64 bytes from cache.google.com (159....): icmp_seq=12 ttl=57 time=5.99 ms
64 bytes from cache.google.com (159...): icmp_seq=13 ttl=57 time=4.96 ms
64 bytes from cache.google.com (159....): icmp_seq=14 ttl=57 time=7.77 ms
64 bytes from cache.google.com (159...): icmp_seq=15 ttl=57 time=1002 ms
64 bytes from cache.google.com (159...): icmp_seq=16 ttl=57 time=430 ms
64 bytes from cache.google.com (159...): icmp_seq=17 ttl=57 time=290 ms
64 bytes from cache.google.com (159...): icmp_seq=18 ttl=57 time=273 ms
64 bytes from cache.google.com (159...): icmp_seq=19 ttl=57 time=228 ms
64 bytes from cache.google.com (159...): icmp_seq=20 ttl=57 time=183 ms
64 bytes from cache.google.com (159...): icmp_seq=21 ttl=57 time=238 ms
64 bytes from cache.google.com (159...): icmp_seq=22 ttl=57 time=121 ms
64 bytes from cache.google.com (159...): icmp_seq=23 ttl=57 time=1732 ms
64 bytes from cache.google.com (159...): icmp_seq=24 ttl=57 time=732 ms
64 bytes from cache.google.com (159...): icmp_seq=25 ttl=57 time=400 ms
64 bytes from cache.google.com (159...): icmp_seq=26 ttl=57 time=912 ms
64 bytes from cache.google.com (159...): icmp_seq=27 ttl=57 time=772 ms
64 bytes from cache.google.com (159...): icmp_seq=28 ttl=57 time=272 ms
64 bytes from cache.google.com (159...): icmp_seq=29 ttl=57 time=355 ms
64 bytes from cache.google.com (159...): icmp_seq=30 ttl=57 time=6.99 ms
64 bytes from cache.google.com (159...): icmp_seq=31 ttl=57 time=5.96 ms
64 bytes from cache.google.com (159...): icmp_seq=32 ttl=57 time=12.7 ms
64 bytes from cache.google.com (159...): icmp_seq=33 ttl=57 time=14.7 ms
64 bytes from cache.google.com (159...): icmp_seq=34 ttl=57 time=87.7 ms
64 bytes from cache.google.com (159...): icmp_seq=35 ttl=57 time=6.93 ms
64 bytes from cache.google.com (159...): icmp_seq=36 ttl=57 time=384 ms
64 bytes from cache.google.com (159...): icmp_seq=37 ttl=57 time=157 ms
64 bytes from cache.google.com (159...): icmp_seq=38 ttl=57 time=20.0 ms
64 bytes from cache.google.com (159...): icmp_seq=39 ttl=57 time=7.00 ms
64 bytes from cache.google.com (159...): icmp_seq=40 ttl=57 time=5.72 ms
64 bytes from cache.google.com (159...): icmp_seq=41 ttl=57 time=175 ms
64 bytes from cache.google.com (159...): icmp_seq=42 ttl=57 time=138 ms
64 bytes from cache.google.com (159...): icmp_seq=43 ttl=57 time=336 ms
64 bytes from cache.google.com (159...): icmp_seq=44 ttl=57 time=305 ms
64 bytes from cache.google.com (159...): icmp_seq=45 ttl=57 time=264 ms
--- google.com ping statistics ---
46 packets transmitted, 45 received, 2% packet loss, time 45056ms
rtt min/avg/max/mdev = 2.358/221.338/1732.050/337.887 ms, pipe 2
使用 VPN 和路由器 Ping 到 Google
连接到 NordVPN 芬兰第一台服务器。最短时间比其他服务器稍长，但稳定性似乎比其他路由器更好。
masi@masi:/etc/openvpn$ ping google.com
PING google.com (159....) 56(84) bytes of data.
64 bytes from cache.google.com (159...): icmp_seq=1 ttl=56 time=1591 ms
64 bytes from cache.google.com (159...): icmp_seq=2 ttl=56 time=2200 ms
64 bytes from cache.google.com (159...): icmp_seq=3 ttl=56 time=1503 ms
64 bytes from cache.google.com (159...): icmp_seq=4 ttl=56 time=2251 ms
64 bytes from cache.google.com (159...): icmp_seq=5 ttl=56 time=1798 ms
64 bytes from cache.google.com (159...): icmp_seq=6 ttl=56 time=850 ms
64 bytes from cache.google.com (159...): icmp_seq=7 ttl=56 time=1618 ms
64 bytes from cache.google.com (159...): icmp_seq=8 ttl=56 time=640 ms
64 bytes from cache.google.com (159...): icmp_seq=9 ttl=56 time=47.4 ms
64 bytes from cache.google.com (159...): icmp_seq=10 ttl=56 time=49.8 ms
64 bytes from cache.google.com (159...): icmp_seq=11 ttl=56 time=43.7 ms
64 bytes from cache.google.com (159...): icmp_seq=12 ttl=56 time=46.2 ms
64 bytes from cache.google.com (159...): icmp_seq=13 ttl=56 time=44.7 ms
64 bytes from cache.google.com (159...): icmp_seq=14 ttl=56 time=46.7 ms
64 bytes from cache.google.com (159...): icmp_seq=15 ttl=56 time=44.9 ms
64 bytes from cache.google.com (159...): icmp_seq=16 ttl=56 time=47.7 ms
64 bytes from cache.google.com (159...): icmp_seq=17 ttl=56 time=53.8 ms
64 bytes from cache.google.com (159...): icmp_seq=18 ttl=56 time=51.0 ms
64 bytes from cache.google.com (159...): icmp_seq=19 ttl=56 time=46.7 ms
64 bytes from cache.google.com (159...): icmp_seq=20 ttl=56 time=44.5 ms
64 bytes from cache.google.com (159...): icmp_seq=21 ttl=56 time=42.8 ms
64 bytes from cache.google.com (159...): icmp_seq=22 ttl=56 time=48.5 ms
64 bytes from cache.google.com (159...): icmp_seq=23 ttl=56 time=43.1 ms
64 bytes from cache.google.com (159...): icmp_seq=24 ttl=56 time=42.2 ms
64 bytes from cache.google.com (159...): icmp_seq=25 ttl=56 time=41.0 ms
64 bytes from cache.google.com (159...): icmp_seq=26 ttl=56 time=43.7 ms
64 bytes from cache.google.com (159...): icmp_seq=27 ttl=56 time=45.7 ms
64 bytes from cache.google.com (159...): icmp_seq=28 ttl=56 time=47.5 ms
64 bytes from cache.google.com (159...): icmp_seq=29 ttl=56 time=41.9 ms
64 bytes from cache.google.com (159...): icmp_seq=30 ttl=56 time=204 ms
64 bytes from cache.google.com (159...): icmp_seq=31 ttl=56 time=211 ms
64 bytes from cache.google.com (159...): icmp_seq=32 ttl=56 time=182 ms
64 bytes from cache.google.com (159...): icmp_seq=33 ttl=56 time=265 ms
64 bytes from cache.google.com (159...): icmp_seq=34 ttl=56 time=239 ms
64 bytes from cache.google.com (159...): icmp_seq=35 ttl=56 time=206 ms
64 bytes from cache.google.com (159...): icmp_seq=36 ttl=56 time=378 ms
64 bytes from cache.google.com (159...): icmp_seq=37 ttl=56 time=215 ms
64 bytes from cache.google.com (159...): icmp_seq=38 ttl=56 time=194 ms
^C
--- google.com ping statistics ---
38 packets transmitted, 38 received, 0% packet loss, time 37465ms
rtt min/avg/max/mdev = 41.088/408.446/2251.809/647.256 ms, pipe 3
我的建议
- ISP 嗅探，因为当我没有使用 VPN 时也丢失过以前的包裹。
- 其他学生嗅探。我的密码非常强，但只有单侧保护，没有两步密码，所以很脆弱。
路由器：TP-Link MR200（用作路由器）
客户端：Asus Zenbook UX303UA、Acer Chromebook 2、Asus 2013 i7 PC、戴尔电脑、联想笔记本电脑、Onelplus two
客户端中的操作系统：Debian 8.5 64 位、Chromebook、Oxygen OS 3.1
互联网协议：IPV4（无设备和无隧道中的 IPV6）