最近 ping 国外的 IP 严重丢包，我大山东的电信线路都丢包。求各路兄弟帮 ping 下结果，帮分析下是国内的问题，还是国外的线路问题？ ping 210.124.1.250 -n 100

V2EX = way to explore

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

现在注册

已注册用户请登录

› DigitalOcean

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

ping

求各路

210.124.1.250

线路

18 条回复 • 2015-12-08 17:36:35 +08:00

yexm0

2015-12-04 14:45:26 +08:00

中国电信大局域网万岁!

rainy3636

2015-12-04 15:07:36 +08:00 via Android

--- 2015 年 12 月 4 日 15:06:40
--- IP (dummy0) fe80::fcb7:11ff:fef6:ba7d%dummy0
--- IP (wlan0) fe80::ee88:92ff:fe6b:cdb9%wlan0
--- IP (wlan0) 10.0.0.1
--- Connection: WIFI

PING 210.124.1.250 (210.124.1.250) 56(84) bytes of data.
64 bytes from 210.124.1.250: icmp_seq=1 ttl=239 time=78.2 ms
64 bytes from 210.124.1.250: icmp_seq=2 ttl=239 time=85.1 ms
64 bytes from 210.124.1.250: icmp_seq=3 ttl=239 time=65.1 ms
64 bytes from 210.124.1.250: icmp_seq=4 ttl=239 time=70.1 ms
64 bytes from 210.124.1.250: icmp_seq=5 ttl=239 time=66.4 ms
64 bytes from 210.124.1.250: icmp_seq=6 ttl=239 time=65.1 ms
64 bytes from 210.124.1.250: icmp_seq=7 ttl=239 time=65.3 ms
64 bytes from 210.124.1.250: icmp_seq=8 ttl=239 time=64.5 ms
64 bytes from 210.124.1.250: icmp_seq=9 ttl=239 time=64.2 ms
64 bytes from 210.124.1.250: icmp_seq=10 ttl=239 time=69.7 ms
64 bytes from 210.124.1.250: icmp_seq=11 ttl=239 time=70.1 ms
64 bytes from 210.124.1.250: icmp_seq=12 ttl=239 time=66.1 ms
64 bytes from 210.124.1.250: icmp_seq=13 ttl=239 time=64.7 ms
64 bytes from 210.124.1.250: icmp_seq=14 ttl=239 time=77.4 ms
64 bytes from 210.124.1.250: icmp_seq=15 ttl=239 time=69.8 ms
64 bytes from 210.124.1.250: icmp_seq=16 ttl=239 time=70.5 ms
64 bytes from 210.124.1.250: icmp_seq=17 ttl=239 time=64.7 ms
64 bytes from 210.124.1.250: icmp_seq=18 ttl=239 time=86.5 ms
64 bytes from 210.124.1.250: icmp_seq=19 ttl=239 time=66.0 ms
64 bytes from 210.124.1.250: icmp_seq=20 ttl=239 time=67.8 ms
64 bytes from 210.124.1.250: icmp_seq=21 ttl=239 time=77.0 ms
64 bytes from 210.124.1.250: icmp_seq=22 ttl=239 time=79.3 ms
64 bytes from 210.124.1.250: icmp_seq=23 ttl=239 time=67.4 ms
64 bytes from 210.124.1.250: icmp_seq=24 ttl=239 time=71.4 ms
64 bytes from 210.124.1.250: icmp_seq=25 ttl=239 time=70.7 ms
64 bytes from 210.124.1.250: icmp_seq=26 ttl=239 time=64.6 ms
64 bytes from 210.124.1.250: icmp_seq=27 ttl=239 time=72.7 ms
64 bytes from 210.124.1.250: icmp_seq=28 ttl=239 time=70.7 ms
64 bytes from 210.124.1.250: icmp_seq=29 ttl=239 time=72.8 ms
64 bytes from 210.124.1.250: icmp_seq=30 ttl=239 time=77.0 ms
64 bytes from 210.124.1.250: icmp_seq=31 ttl=239 time=65.3 ms
64 bytes from 210.124.1.250: icmp_seq=32 ttl=239 time=64.2 ms
64 bytes from 210.124.1.250: icmp_seq=33 ttl=239 time=65.5 ms
64 bytes from 210.124.1.250: icmp_seq=34 ttl=239 time=71.1 ms
64 bytes from 210.124.1.250: icmp_seq=35 ttl=239 time=71.0 ms
64 bytes from 210.124.1.250: icmp_seq=36 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=37 ttl=239 time=70.1 ms
64 bytes from 210.124.1.250: icmp_seq=38 ttl=239 time=67.6 ms
64 bytes from 210.124.1.250: icmp_seq=39 ttl=239 time=85.4 ms
64 bytes from 210.124.1.250: icmp_seq=40 ttl=239 time=75.6 ms
64 bytes from 210.124.1.250: icmp_seq=41 ttl=239 time=74.4 ms
64 bytes from 210.124.1.250: icmp_seq=42 ttl=239 time=71.3 ms
64 bytes from 210.124.1.250: icmp_seq=43 ttl=239 time=69.9 ms
64 bytes from 210.124.1.250: icmp_seq=44 ttl=239 time=72.6 ms
64 bytes from 210.124.1.250: icmp_seq=45 ttl=239 time=71.3 ms
64 bytes from 210.124.1.250: icmp_seq=46 ttl=239 time=64.1 ms
64 bytes from 210.124.1.250: icmp_seq=47 ttl=239 time=67.0 ms
64 bytes from 210.124.1.250: icmp_seq=48 ttl=239 time=65.4 ms
64 bytes from 210.124.1.250: icmp_seq=49 ttl=239 time=70.0 ms
64 bytes from 210.124.1.250: icmp_seq=50 ttl=239 time=69.4 ms
64 bytes from 210.124.1.250: icmp_seq=51 ttl=239 time=66.7 ms
64 bytes from 210.124.1.250: icmp_seq=52 ttl=239 time=64.9 ms
64 bytes from 210.124.1.250: icmp_seq=53 ttl=239 time=70.6 ms
64 bytes from 210.124.1.250: icmp_seq=54 ttl=239 time=65.9 ms
64 bytes from 210.124.1.250: icmp_seq=55 ttl=239 time=64.3 ms
64 bytes from 210.124.1.250: icmp_seq=56 ttl=239 time=74.8 ms
64 bytes from 210.124.1.250: icmp_seq=57 ttl=239 time=65.1 ms
64 bytes from 210.124.1.250: icmp_seq=58 ttl=239 time=70.0 ms
64 bytes from 210.124.1.250: icmp_seq=59 ttl=239 time=76.1 ms
64 bytes from 210.124.1.250: icmp_seq=60 ttl=239 time=66.3 ms
64 bytes from 210.124.1.250: icmp_seq=61 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=62 ttl=239 time=66.9 ms
64 bytes from 210.124.1.250: icmp_seq=63 ttl=239 time=69.3 ms
64 bytes from 210.124.1.250: icmp_seq=64 ttl=239 time=70.4 ms
64 bytes from 210.124.1.250: icmp_seq=65 ttl=239 time=69.2 ms
64 bytes from 210.124.1.250: icmp_seq=66 ttl=239 time=71.6 ms
64 bytes from 210.124.1.250: icmp_seq=67 ttl=239 time=70.4 ms
64 bytes from 210.124.1.250: icmp_seq=68 ttl=239 time=69.9 ms
64 bytes from 210.124.1.250: icmp_seq=69 ttl=239 time=77.9 ms
64 bytes from 210.124.1.250: icmp_seq=70 ttl=239 time=69.8 ms
64 bytes from 210.124.1.250: icmp_seq=71 ttl=239 time=76.7 ms
64 bytes from 210.124.1.250: icmp_seq=72 ttl=239 time=83.7 ms
64 bytes from 210.124.1.250: icmp_seq=73 ttl=239 time=70.1 ms
64 bytes from 210.124.1.250: icmp_seq=74 ttl=239 time=64.9 ms
64 bytes from 210.124.1.250: icmp_seq=75 ttl=239 time=68.7 ms
64 bytes from 210.124.1.250: icmp_seq=76 ttl=239 time=72.6 ms
64 bytes from 210.124.1.250: icmp_seq=77 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=78 ttl=239 time=66.1 ms
64 bytes from 210.124.1.250: icmp_seq=79 ttl=239 time=71.0 ms
64 bytes from 210.124.1.250: icmp_seq=80 ttl=239 time=65.5 ms
64 bytes from 210.124.1.250: icmp_seq=81 ttl=239 time=73.2 ms
64 bytes from 210.124.1.250: icmp_seq=82 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=83 ttl=239 time=70.7 ms
64 bytes from 210.124.1.250: icmp_seq=84 ttl=239 time=72.6 ms
64 bytes from 210.124.1.250: icmp_seq=85 ttl=239 time=64.4 ms
64 bytes from 210.124.1.250: icmp_seq=86 ttl=239 time=100 ms
64 bytes from 210.124.1.250: icmp_seq=87 ttl=239 time=70.2 ms
64 bytes from 210.124.1.250: icmp_seq=88 ttl=239 time=73.2 ms
64 bytes from 210.124.1.250: icmp_seq=89 ttl=239 time=69.3 ms
64 bytes from 210.124.1.250: icmp_seq=90 ttl=239 time=70.4 ms
64 bytes from 210.124.1.250: icmp_seq=91 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=92 ttl=239 time=82.7 ms
64 bytes from 210.124.1.250: icmp_seq=93 ttl=239 time=69.9 ms
64 bytes from 210.124.1.250: icmp_seq=94 ttl=239 time=73.8 ms
64 bytes from 210.124.1.250: icmp_seq=95 ttl=239 time=73.5 ms
64 bytes from 210.124.1.250: icmp_seq=96 ttl=239 time=71.0 ms
64 bytes from 210.124.1.250: icmp_seq=97 ttl=239 time=69.8 ms
64 bytes from 210.124.1.250: icmp_seq=98 ttl=239 time=72.6 ms
64 bytes from 210.124.1.250: icmp_seq=99 ttl=239 time=70.3 ms
64 bytes from 210.124.1.250: icmp_seq=100 ttl=239 time=70.0 ms

--- 210.124.1.250 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 102145ms
min = 64.183 ms
avg = 70.863 ms
max = 100.484 ms
mdev = 5.687 ms

ytman

2015-12-04 15:13:31 +08:00

@rainy3636 兄弟用的联通还是电信？为毛速度这么快？

ytman

2015-12-04 15:14:17 +08:00

@yexm0 感谢测试，朋友们都说联通访问韩国的国际出口速度比电信好。

rainy3636

2015-12-04 15:20:12 +08:00 via Android

@ytman 沈阳联通

alect

2015-12-04 15:26:03 +08:00

安徽电信

ytman

2015-12-04 16:28:09 +08:00

@alect 看来安徽的电信线路也不太好啊

finab

2015-12-04 16:32:51 +08:00

北京联通

LINAICAI

2015-12-04 16:40:21 +08:00

http://imgur.com/BD6OuXV

LINAICAI

2015-12-04 16:42:07 +08:00

怎么贴图啊。。。最近服务器丢包严重，香港主机也不例外。。。

kttde

2015-12-04 16:53:17 +08:00

Marfal

2015-12-04 17:24:09 +08:00

上海电信

snsd

2015-12-05 12:18:46 +08:00

@rainy3636 沈阳联通出口也在北京联通上面啊

ytman

2015-12-08 08:57:49 +08:00

@a33004407
大哥的 28 毫秒的延迟，比同省的速度都快，小弟崇拜如滔滔江水.

我山东电信，能否也走 @a33004407 这条线路出口到韩国？

访问韩国的这个 IP 210.124.1.250 丢包很严重，找过当地电信机房的负责人，对方称无权更换目前的路由出口节点，必须更换公网 IP 地址，即更换到中国电信 CN2 线路（测试过，一般是 59.43.x.x 开头的 IP,从北京电信出口）

可是更换 IP 相当麻烦，使用多年的各种软件、 VPN 都要修改测试，有什么办法能保留现有 IP ，修改国际出口呢？

各位有空帮忙给点意见吧？
@yexm0
@rainy3636
@alect
@LINAICAI
@LINAICAI
@kttde

附测试结果：

（ 1 ） tracert
Tracing route to 210.124.1.250 over a maximum of 30 hops
1 1 ms <1 ms 2 ms 192.168.1.1 局域网对方和您在同一内部网
2 2 ms 3 ms 4 ms 222.173.206.241 山东省烟台市电信
3 6 ms 3 ms 1 ms 60.235.66.137 山东省滨州市电信
4 13 ms 8 ms 9 ms 60.235.64.61 山东省滨州市电信
5 20 ms 19 ms 20 ms 202.97.39.25 中国电信骨干网
6 21 ms 22 ms 19 ms 202.97.33.10 上海市电信骨干网
7 * * * Request timed out.
8 23 ms 23 ms * 202.97.60.10 中国电信骨干网
9 * 45 ms * 211.40.6.157 韩国
10 * 86 ms 86 ms 210.120.103.221 韩国
11 43 ms 88 ms 91 ms 1.208.151.194 韩国
12 50 ms 182 ms 41 ms 1.208.148.238 韩国
13 * * 91 ms 1.208.148.66 韩国
14 89 ms 88 ms * 1.209.52.106 韩国
15 90 ms * 89 ms 112.217.255.94 韩国
16 * * * Request timed out.
17 * * * Request timed out.
18 * * 49 ms 210.124.1.250 韩国 LG Dacom
Trace complete. 210.124.1.250 韩国 LG Dacom

（ 2 ） ping
ping 210.124.1.250 -t

正在 Ping 210.124.1.250 具有 32 字节的数据:
请求超时。
请求超时。
请求超时。
来自 210.124.1.250 的回复: 字节=32 时间=42ms TTL=238
来自 210.124.1.250 的回复: 字节=32 时间=88ms TTL=237
来自 210.124.1.250 的回复: 字节=32 时间=42ms TTL=238
来自 210.124.1.250 的回复: 字节=32 时间=49ms TTL=238
请求超时。
请求超时。
来自 210.124.1.250 的回复: 字节=32 时间=49ms TTL=238

210.124.1.250 的 Ping 统计信息:
数据包: 已发送 = 123 ，已接收 = 66 ，丢失 = 57 (46% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 42ms ，最长 = 93ms ，平均 = 60ms
Control-C

yexm0

2015-12-08 10:40:34 +08:00 via Android

保留 ip 换线路不太可能。

rainy3636

2015-12-08 13:03:06 +08:00 via Android

@ytman
买下 ip 段，申请 AS 号， BGP

我想问问

rainy3636

2015-12-08 13:04:20 +08:00 via Android

@ytman 那个韩国 ip 是哪的服务器或 vps ？

ytman

2015-12-08 17:36:35 +08:00

@rainy3636 那个韩国的 IP 使用的是韩国 LGdacom 公司的线路，是一个小办公室。
我们平时之间有 VPN 通信。

最近 ping 国外的 IP 严重丢包，我大山东的电信线路 都丢包。 求各路 兄弟帮 ping 下结果，帮分析下是国内的问题，还是国外的线路问题？ ping 210.124.1.250 -n 100

最近 ping 国外的 IP 严重丢包，我大山东的电信线路都丢包。求各路兄弟帮 ping 下结果，帮分析下是国内的问题，还是国外的线路问题？ ping 210.124.1.250 -n 100