1
laucie OP 自己顶一下
|
2
tinkerer 2015-08-02 21:44:08 +08:00
正在 Ping github.com [192.30.252.131] 具有 32 字节的数据:
来自 192.30.252.131 的回复: 字节=32 时间=346ms TTL=52 来自 192.30.252.131 的回复: 字节=32 时间=346ms TTL=52 来自 192.30.252.131 的回复: 字节=32 时间=860ms TTL=52 来自 192.30.252.131 的回复: 字节=32 时间=343ms TTL=52 192.30.252.131 的 Ping 统计信息: 数据包: 已发送 = 4,已接收 = 4,丢失 = 0 (0% 丢失), 往返行程的估计时间(以毫秒为单位): 最短 = 343ms,最长 = 860ms,平均 = 473ms |
3
laucie OP @tinkerer 我这里帝都联通
Request timeout for icmp_seq 161 Request timeout for icmp_seq 162 Request timeout for icmp_seq 163 Request timeout for icmp_seq 164 Request timeout for icmp_seq 165 Request timeout for icmp_seq 166 Request timeout for icmp_seq 167 Request timeout for icmp_seq 168 ^C --- github.com ping statistics --- 170 packets transmitted, 7 packets received, 95.9% packet loss |
4
hinate 2015-08-02 21:46:58 +08:00
我这里帝都联通 请求超时
|
5
chanssl 2015-08-02 21:48:36 +08:00
Pinging github.com [192.30.252.128] with 32 bytes of d
Request timed out. Request timed out. Reply from 192.30.252.128: bytes=32 time=493ms TTL=50 Reply from 192.30.252.128: bytes=32 time=499ms TTL=50 Ping statistics for 192.30.252.128: Packets: Sent = 4, Received = 2, Lost = 2 (50% los Approximate round trip times in milli-seconds: Minimum = 493ms, Maximum = 499ms, Average = 496ms |
7
TakanashiAzusa 2015-08-02 21:52:07 +08:00
@laucie 看报错信息就知道问题在哪了。。
|
8
laucie OP @TakanashiAzusa就是超时
|
9
chenbojian 2015-08-02 21:57:17 +08:00
同帝都联通,超时
|
10
laucie OP @chenbojian 貌似是出口出问题了 我用ss 就能上去
|
11
chenbojian 2015-08-02 22:04:30 +08:00
@laucie git设置了代理之后就可以了,我用的windows,好像git默认是总是不用系统代理的
|
12
Livid MOD |
13
woodrat 2015-08-02 22:30:11 +08:00
同帝都联通,超时
|
14
aveline 2015-08-03 13:02:04 +08:00
|