出现这种情况是不是可以判断是网络有问题?

2016-11-17 17:39:24 +08:00
 83f420984

同时 ping 路由与百度,发现百度(换成阿里 DNS 、 114 都会这样)会出现掉包,而路由确没有掉包,能说明是网络的问题么?已经重启过路由、光猫、换过DNS ,还是会掉包。

ping 路由器

64 bytes from 192.168.99.1: icmp_seq=51 ttl=64 time=1.852 ms
64 bytes from 192.168.99.1: icmp_seq=52 ttl=64 time=1.856 ms
64 bytes from 192.168.99.1: icmp_seq=53 ttl=64 time=2.603 ms
64 bytes from 192.168.99.1: icmp_seq=54 ttl=64 time=1.761 ms
64 bytes from 192.168.99.1: icmp_seq=55 ttl=64 time=2.290 ms
64 bytes from 192.168.99.1: icmp_seq=56 ttl=64 time=2.099 ms
64 bytes from 192.168.99.1: icmp_seq=57 ttl=64 time=1.334 ms
64 bytes from 192.168.99.1: icmp_seq=58 ttl=64 time=1.810 ms
64 bytes from 192.168.99.1: icmp_seq=59 ttl=64 time=1.796 ms
64 bytes from 192.168.99.1: icmp_seq=60 ttl=64 time=2.437 ms
64 bytes from 192.168.99.1: icmp_seq=61 ttl=64 time=2.427 ms
64 bytes from 192.168.99.1: icmp_seq=62 ttl=64 time=1.873 ms
64 bytes from 192.168.99.1: icmp_seq=63 ttl=64 time=1.764 ms
64 bytes from 192.168.99.1: icmp_seq=64 ttl=64 time=1.742 ms
64 bytes from 192.168.99.1: icmp_seq=65 ttl=64 time=1.992 ms
64 bytes from 192.168.99.1: icmp_seq=66 ttl=64 time=3.244 ms
64 bytes from 192.168.99.1: icmp_seq=67 ttl=64 time=2.024 ms
64 bytes from 192.168.99.1: icmp_seq=68 ttl=64 time=1.793 ms
64 bytes from 192.168.99.1: icmp_seq=69 ttl=64 time=2.581 ms
64 bytes from 192.168.99.1: icmp_seq=70 ttl=64 time=2.088 ms
64 bytes from 192.168.99.1: icmp_seq=71 ttl=64 time=2.091 ms

ping baidu.com

64 bytes from 111.13.101.208: icmp_seq=55 ttl=52 time=37.205 ms
64 bytes from 111.13.101.208: icmp_seq=56 ttl=52 time=36.764 ms
64 bytes from 111.13.101.208: icmp_seq=57 ttl=52 time=35.782 ms
Request timeout for icmp_seq 58
64 bytes from 111.13.101.208: icmp_seq=59 ttl=52 time=45.813 ms
64 bytes from 111.13.101.208: icmp_seq=60 ttl=52 time=36.066 ms
64 bytes from 111.13.101.208: icmp_seq=61 ttl=52 time=37.295 ms
64 bytes from 111.13.101.208: icmp_seq=62 ttl=52 time=36.391 ms
64 bytes from 111.13.101.208: icmp_seq=63 ttl=52 time=37.007 ms
64 bytes from 111.13.101.208: icmp_seq=64 ttl=52 time=45.562 ms
64 bytes from 111.13.101.208: icmp_seq=65 ttl=52 time=37.295 ms
64 bytes from 111.13.101.208: icmp_seq=66 ttl=52 time=36.604 ms
64 bytes from 111.13.101.208: icmp_seq=67 ttl=52 time=36.875 ms
64 bytes from 111.13.101.208: icmp_seq=68 ttl=52 time=35.884 ms
64 bytes from 111.13.101.208: icmp_seq=69 ttl=52 time=37.108 ms
64 bytes from 111.13.101.208: icmp_seq=70 ttl=52 time=35.864 ms
Request timeout for icmp_seq 71
64 bytes from 111.13.101.208: icmp_seq=72 ttl=52 time=36.965 ms
64 bytes from 111.13.101.208: icmp_seq=73 ttl=52 time=38.821 ms

--- baidu.com ping statistics ---
116 packets transmitted, 114 packets received, 1.7% packet loss
round-trip min/avg/max/stddev = 35.291/37.316/45.813/1.543 ms
3127 次点击
所在节点    宽带症候群
11 条回复
akwIX
2016-11-17 18:00:38 +08:00
111.13.101.208 这个是北京移动

你如果是移动的话,那是网络问题

如果不是移动的话,是 dns 解析的问题
d7101120120
2016-11-17 18:06:13 +08:00
111.13.101.208 的 Ping 统计信息:
数据包: 已发送 = 148 ,已接收 = 146 ,丢失 = 2 (1% 丢失),
往返行程的估计时间(以毫秒为单位):
最短 = 4ms ,最长 = 26ms ,平均 = 7ms

北京鹏博士这边也丢包。不过这种低丢包率似乎没什么影响。
ovear
2016-11-17 18:06:54 +08:00
- -你得 ping 出口路由呀
83f420984
2016-11-17 18:13:28 +08:00
@ovear 不太懂出口路由,我 ping 的这个路由是直接连接的桥接的光猫,算出口么路由吗?
LGA1150
2016-11-17 19:00:09 +08:00
ovear
2016-11-17 20:31:51 +08:00
@83f420984 tracert qq.com
第一个公网 ip 就是出口路由
z991238
2016-11-17 21:18:14 +08:00
= =国内网站 ping 起来都有少数丢包。这不是运营商问题。是本身他们 BGP 线路问题。是正常的
29EtwXn6t5wgM3fD
2016-11-18 09:35:41 +08:00
用路由器的诊断功能 ping 了看看
LGA1150
2016-11-18 10:29:31 +08:00
@d7101120120
@shengyu
@z991238
@83f420984
baidu.com 根域没有做分区解析,请 ping www.baidu.com
alect
2016-11-18 18:00:05 +08:00
你这路由看起来也不咋滴啊
83f420984
2016-11-18 18:05:32 +08:00
@alect 几十块的路由

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/321246

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX