64 bytes from 10.0.0.254: icmp_seq=93 ttl=64 time=18.734 ms
64 bytes from 10.0.0.254: icmp_seq=94 ttl=64 time=7.145 ms
64 bytes from 10.0.0.254: icmp_seq=95 ttl=64 time=3.203 ms
64 bytes from 10.0.0.254: icmp_seq=96 ttl=64 time=65.056 ms
64 bytes from 10.0.0.254: icmp_seq=97 ttl=64 time=3.944 ms
64 bytes from 10.0.0.254: icmp_seq=98 ttl=64 time=51.942 ms
64 bytes from 10.0.0.254: icmp_seq=99 ttl=64 time=4.197 ms
64 bytes from 10.0.0.254: icmp_seq=100 ttl=64 time=5.125 ms
64 bytes from 10.0.0.254: icmp_seq=101 ttl=64 time=101.515 ms
64 bytes from 10.0.0.254: icmp_seq=102 ttl=64 time=5.378 ms
64 bytes from 10.0.0.254: icmp_seq=103 ttl=64 time=82.837 ms
64 bytes from 10.0.0.254: icmp_seq=104 ttl=64 time=5.464 ms
64 bytes from 10.0.0.254: icmp_seq=105 ttl=64 time=3.651 ms
64 bytes from 10.0.0.254: icmp_seq=106 ttl=64 time=5.906 ms
64 bytes from 10.0.0.254: icmp_seq=107 ttl=64 time=5.129 ms
64 bytes from 10.0.0.254: icmp_seq=108 ttl=64 time=5.056 ms
64 bytes from 10.0.0.254: icmp_seq=109 ttl=64 time=5.050 ms
64 bytes from 10.0.0.254: icmp_seq=110 ttl=64 time=5.313 ms
mac: m1
windows: ax201
同样的环境,同样同时连同一个 WIFI ,windows 最高只有 4ms.这种除了换 WIFI ,还有其他解决方案么?
路由器为 TP 的 XTR5466
1
cwcc 2022-07-30 15:56:09 +08:00
一般这种情况都优先控制变量,比如换个路由器,操作系统统一(当然 M1 那没办法了),位置变换,网卡变换。有时候别说无线,就算是有线网卡这种情况也几乎随时都可能出现。
|
2
cnbatch 2022-07-30 18:28:43 +08:00
可能是 M1 的锅,去年就有人遇到过 M1 的 wifi 有问题:
https://www.v2ex.com/t/753441 |
4
huaes 2022-07-30 18:39:48 +08:00
看看周围有没有什么电磁干扰,别说无线了,MAC 有线都能让对讲机整断流
|
5
auser 2022-07-30 19:19:27 +08:00 1
前段时间花了大量时间排查并解决了这个问题:
解决方案 1:把 Universal Control 功能关闭后稍等片刻或者重启系统 (推荐) 解决方案 2: 终端执行 sudo ifconfig awdl0 down (不推荐) 关闭 Universal Control 后 ping 网关的延迟恢复正常,开启后问题再次出现。 上述问题在 intel i9/m1 max 芯片的 MacBook Pro 16 上均存在。 |
6
cwcc 2022-07-30 19:59:38 +08:00
@wsseo 有线有可能的,有可能是路由器那端,比如软路由的配置没配好就容易出现,还有 USB 网卡质量参差不齐,有的会有丢包或重发 TCP 包等情况,我之前买的一个便宜的扩展坞就是。
|
7
blakejia OP 测试下来,和路由器应该关系不大。换了小米的基本是同样的表现。
|
8
berry10086 2022-07-31 22:47:08 +08:00
是 mac 的问题
装个 wifriedx 禁掉 airdrop 就好了 |
9
berry10086 2022-07-31 22:48:25 +08:00
关 awdl/airdrop
``` 64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=3.821 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.221 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.328 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.112 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.884 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=4.092 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=5.382 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.653 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.107 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.249 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.067 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=3.222 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=5.198 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.333 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=3.974 ms 64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=4.346 ms ``` 开 awdl/airdrop ``` 64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=286.417 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.403 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.623 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.573 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.206 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=8.656 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=4.552 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=24.615 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.897 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=4.480 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.705 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=49.136 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=92.310 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4.602 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=4.451 ms ``` |
10
blakejia OP |
11
berry10086 2022-08-01 09:38:50 +08:00
@blakejia 我用过的所有路由器,都可以复现这个现象。mac 一直在后台扫描 wifi ,扫描时延迟就大。关了 airdrop 后恢复
|
12
zxsky1 2022-09-07 02:04:33 +08:00
@berry10086 解决了,非常感谢。
几年不登录 V2EX 了,搜到了解决方案哈哈,感谢。 |