如何解决 mtr 首跳丢包率 50% 的问题

如何解决 mtr 首跳丢包率 50% 的问题

我已经将 mtr 运行到 8.8.8.8。在第一次跳转到 142.254.191.13 时,数据包丢失率高达 50%。这些问题大约在 24 小时前开始出现,并且经常波动。每次我都能有 2-5 分钟的良好网络,然后速度就会变得非常慢。加载一个简单的网页可能需要 30 秒以上。

这说明我的数据包在哪里丢失了?是我的配置有问题,还是 Spectrum 端存在问题?

我该如何进一步诊断这个问题?

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                    ubnt -    0 |  316 |  316 |    0 |    0 |    0 |    0 |
|                          142.254.191.13 -   51 |  104 |   51 |    0 |   22 |  117 |   11 |
|      xe-0-0-4.hnllhiku01h.hawaii.rr.com -   50 |  107 |   54 |    0 |   57 |  405 |   29 |
|         agg37.milnhixd01r.hawaii.rr.com -   57 |   98 |   43 |    8 |   22 |   55 |   18 |
|          agg31.lsancarc01r.socal.rr.com -   55 |   99 |   45 |   53 |   68 |  121 |   57 |
|bu-ether16.lsancarc0yw-bcr00.tbone.rr.com -   49 |  108 |   56 |   59 |   75 |  132 |   67 |
|                           74.125.48.188 -   51 |  104 |   51 |   56 |   68 |  102 |   60 |
|                          64.233.174.209 -   47 |  110 |   59 |   60 |   76 |  175 |   63 |
|                         142.250.228.235 -   51 |  104 |   51 |   59 |   74 |  106 |   61 |
|                              dns.google -   50 |  106 |   53 |   58 |   73 |  105 |   68 |
|________________________________________________|______|______|______|______|______|______|                              

当我完全绕过路由器并直接插入调制解调器时,我看到的是这样的:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          142.254.191.13 -   56 |   18 |    8 |    9 |   18 |   33 |   21 |
|         agg61.hnllhiku01h.hawaii.rr.com -   41 |   22 |   13 |   17 |   48 |  163 |  163 |
|         agg37.milnhixd01r.hawaii.rr.com -   56 |   18 |    8 |    9 |   23 |   49 |   21 |
|          agg31.lsancarc01r.socal.rr.com -   41 |   22 |   13 |   54 |   65 |   94 |   67 |
|bu-ether26.lsancarc0yw-bcr00.tbone.rr.com -   41 |   22 |   13 |   59 |   72 |  100 |   75 |
|                            74.125.49.40 -   41 |   22 |   13 |   57 |   68 |   97 |   70 |
|                           74.125.253.15 -   41 |   22 |   13 |   63 |   74 |  103 |   75 |
|                           216.239.46.97 -   56 |   18 |    8 |   57 |   71 |   97 |   70 |
|                              dns.google -   41 |   22 |   13 |   59 |   70 |   99 |   71 |
|________________________________________________|______|______|______|______|______|______|

在我的调制解调器日志中,我几乎每分钟都会看到这种情况。

Sat Aug 15 19:19:14 2020    Critical (3)    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:9b:98;CMTS-MAC=00:01:5c:76:6c:59;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 19:10:46 2020    Warning (5) ToD request sent- No Response received;CM-MAC=08:36:c9:3f:9b:98;CMTS-MAC=00:01:5c:76:6c:59;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 19:10:30 2020    Critical (3)    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:9b:98;CMTS-MAC=00:01:5c:76:6c:59;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 19:10:13 2020    Warning (5) ToD request sent- No Response received;CM-MAC=08:36:c9:3f:9b:98;CMTS-MAC=00:01:5c:76:6c:59;CM-QOS=1.1;CM-VER=3.1;

相关内容