PDA

光世代10M/2M的ping值



贊助商連結

頁 : 1 [2]
wefo
2010-05-06, 12:27 PM
我的都是 7ms ，感覺很差
剛才TRACERT 樓主那幾個點，怎麼都是等候逾時 ?
是因為IP 分享器的關係嗎 ?
也許吧，小弟測試時是直接接數據機哦

贊助商連結

timliu28
2010-05-12, 10:02 AM
我家測都26ms左右
打電話問中華的工程師結果他說100ms以下都正常,你26ms已經很好了啦!
kouyoumin
2010-05-17, 03:30 PM
我家測都26ms左右
打電話問中華的工程師結果他說100ms以下都正常,你26ms已經很好了啦!
100ms以下都算正常的話
那您就把照三餐報修也當正常好了
p055877632
2010-05-17, 03:47 PM
TINP速博路由 ping google dns

C:\Documents and Settings\Administrator>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=25ms TTL=54
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=23ms TTL=54
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=20ms TTL=54
Reply from 8.8.8.8: bytes=32 time=63ms TTL=54
Reply from 8.8.8.8: bytes=32 time=23ms TTL=54
Reply from 8.8.8.8: bytes=32 time=20ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54
Reply from 8.8.8.8: bytes=32 time=22ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=20ms TTL=54
Reply from 8.8.8.8: bytes=32 time=20ms TTL=54
Reply from 8.8.8.8: bytes=32 time=23ms TTL=54
Reply from 8.8.8.8: bytes=32 time=23ms TTL=54
Reply from 8.8.8.8: bytes=32 time=24ms TTL=54
Reply from 8.8.8.8: bytes=32 time=19ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54
Reply from 8.8.8.8: bytes=32 time=21ms TTL=54

Ping statistics for 8.8.8.8:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 63ms, Average = 23ms

ping hinet dns
C:\Documents and Settings\Administrator>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=22ms TTL=244
Reply from 168.95.1.1: bytes=32 time=19ms TTL=244
Reply from 168.95.1.1: bytes=32 time=19ms TTL=243
Reply from 168.95.1.1: bytes=32 time=24ms TTL=244
Reply from 168.95.1.1: bytes=32 time=24ms TTL=243
Reply from 168.95.1.1: bytes=32 time=19ms TTL=243
Reply from 168.95.1.1: bytes=32 time=19ms TTL=244
Reply from 168.95.1.1: bytes=32 time=19ms TTL=243
Reply from 168.95.1.1: bytes=32 time=22ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=21ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=18ms TTL=244
Reply from 168.95.1.1: bytes=32 time=19ms TTL=243
Reply from 168.95.1.1: bytes=32 time=20ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=244
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243
Reply from 168.95.1.1: bytes=32 time=23ms TTL=243

Ping statistics for 168.95.1.1:
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 24ms, Average = 21ms

ping yahoo
C:\Documents and Settings\Administrator>ping www.yahoo.com.tw -t

Pinging tpc-w2.rd.tw.g1.b.yahoo.com [203.84.202.10] with 32 bytes of data:

Reply from 203.84.202.10: bytes=32 time=21ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=38ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=21ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=24ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=18ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=19ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55
Reply from 203.84.202.10: bytes=32 time=20ms TTL=55

Ping statistics for 203.84.202.10:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 38ms, Average = 19ms

我只po 結果
不多說什麼 要不然某大濕又要出來炮了
niwa
2010-05-17, 03:48 PM
100ms以下都算正常的話
那您就把照三餐報修也當正常好了

我用 VDSL 10M/2M 跑起來還沒看過超過 50ms 超過的話建議三餐打電話報修好了
剛剛簡易測試結果

tracert 168.95.1.1

Tracing route to dns.hinet.net [168.95.1.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 211-21-205-254.HINET-IP.hinet.net [211.21.205.254]
2 1 ms 1 ms 1 ms tc-c76r1.router.hinet.net [168.95.144.210]
3 1 ms 1 ms 1 ms tc-c12r11.router.hinet.net [220.128.16.142]
4 1 ms 1 ms 1 ms 202-39-179-185.HINET-IP.hinet.net [202.39.179.185]
5 2 ms 2 ms 2 ms dns.hinet.net [168.95.1.1]

Trace complete.

ping 168.95.1.1

Reply from 168.95.1.1: bytes=32 time=2ms TTL=249
Reply from 168.95.1.1: bytes=32 time=2ms TTL=249
Reply from 168.95.1.1: bytes=32 time=1ms TTL=249
Reply from 168.95.1.1: bytes=32 time=1ms TTL=249

Ping 8.8.8.8

Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53

Ping www.yahoo.com.tw

Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
spooky_mulder
2010-05-17, 07:26 PM
我用 VDSL 10M/2M 跑起來還沒看過超過 50ms 超過的話建議三餐打電話報修好了
剛剛簡易測試結果

ping 168.95.1.1

Reply from 168.95.1.1: bytes=32 time=2ms TTL=249
Reply from 168.95.1.1: bytes=32 time=2ms TTL=249
Reply from 168.95.1.1: bytes=32 time=1ms TTL=249
Reply from 168.95.1.1: bytes=32 time=1ms TTL=249

Ping 8.8.8.8

Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53
Reply from 8.8.8.8: bytes=32 time=5ms TTL=53

Ping www.yahoo.com.tw

Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56
Reply from 119.160.246.23: bytes=32 time=4ms TTL=56



你的回應時間一看就知道不是 VDSL 供裝的了，這種回應時間一定是 FTTH 供裝的。

以下這些值才像是 VDSL 供裝的回應時間：

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=17ms TTL=247
Reply from 168.95.1.1: bytes=32 time=17ms TTL=247
Reply from 168.95.1.1: bytes=32 time=17ms TTL=247
Reply from 168.95.1.1: bytes=32 time=18ms TTL=247


Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53


ping tw.yahoo.com
Pinging tw1-w2.rd.tw.g1.b.yahoo.com [119.160.246.23] with 32 bytes of data:

Reply from 119.160.246.23: bytes=32 time=17ms TTL=56
Reply from 119.160.246.23: bytes=32 time=18ms TTL=56
Reply from 119.160.246.23: bytes=32 time=17ms TTL=56
Reply from 119.160.246.23: bytes=32 time=17ms TTL=56
niwa
2010-05-17, 10:52 PM
你的回應時間一看就知道不是 VDSL 供裝的了，這種回應時間一定是 FTTH 供裝的。

以下這些值才像是 VDSL 供裝的回應時間：


打習慣了改不了
一般 VDSL 通常不會超過 50ms 如果超過幾乎是有問題了

話說我線路由 ZyXel MGS-3712C 改成 首特 AF-101R 設備 (多台)
前幾天 ZyXel 的電源燒掉 全部都斷線 外面訂單資料傳不進來損失慘重 (人在北部無法回去處理)
後來改成 AF-101R 多台施工人員說這樣比較安全
2M/2M專線還是保持在 MGS-3712 其餘都移出來接在 AF-101R
spooky_mulder
2010-05-17, 11:18 PM
打習慣了改不了
一般 VDSL 通常不會超過 50ms 如果超過幾乎是有問題了

話說我線路由 ZyXel MGS-3712C 改成 首特 AF-101R 設備 (多台)
前幾天 ZyXel 的電源燒掉 全部都斷線 外面訂單資料傳不進來損失慘重 (人在北部無法回去處理)
後來改成 AF-101R 多台施工人員說這樣比較安全
2M/2M專線還是保持在 MGS-3712 其餘都移出來接在 AF-101R

看來你生意做滿大的。

一般 VDSL 會不會超過 50ms 要看 ping 到哪個點， ping 到 gatewat 或 ISP DNS，正常狀況下我也還沒有看過超過 50ms的。
小沛
2010-05-18, 01:18 AM
VDSL 10M/2M

C:\Documents and Settings\Administrator>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248

Ping statistics for 168.95.1.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 13ms, Average = 13ms
Control-C
^C
C:\Documents and Settings\Administrator>

C:\>tracert 168.95.1.1

Tracing route to dns.hinet.net [168.95.1.1]
over a maximum of 30 hops:

1 12 ms 12 ms 12 ms h254.s98.ts.hinet.net [168.95.98.254]
2 12 ms 12 ms 11 ms hc-c76r2.router.hinet.net [168.95.91.98]
3 11 ms 11 ms 11 ms hc-c12r2.router.hinet.net [211.22.38.178]
4 13 ms 13 ms 13 ms tp-crs12.router.hinet.net [220.128.2.34]
5 13 ms 13 ms 12 ms tp-s2-c12r2.router.hinet.net [220.128.2.217]
6 18 ms 14 ms 21 ms 210-59-204-189.HINET-IP.hinet.net [210.59.204.18
9]
7 13 ms 13 ms 13 ms dns.hinet.net [168.95.1.1]


C:\>tracert tw.yahoo.com

Tracing route to tw-tpe-fo.fyap.b.yahoo.com [119.160.246.241]
over a maximum of 30 hops:

1 12 ms 12 ms 12 ms h254.s98.ts.hinet.net [168.95.98.254]
2 12 ms 11 ms 12 ms hc-c76r2.router.hinet.net [168.95.91.98]
3 11 ms 12 ms 11 ms hc-c12r1.router.hinet.net [211.22.38.78]
4 18 ms 16 ms 15 ms tp-crs11.router.hinet.net [220.128.1.34]
5 14 ms 14 ms 14 ms tp-s2-mx01.router.hinet.net [220.128.3.149]
6 16 ms 16 ms 16 ms 211.22.41.45
7 15 ms 15 ms 14 ms te-8-1.bas2-1-prd.tw1.yahoo.com [119.160.240.3]

8 15 ms 15 ms 22 ms w1.www.vip.tw1.yahoo.com [119.160.246.241]

Trace complete.

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 12 ms 12 ms 12 ms h254.s98.ts.hinet.net [168.95.98.254]
2 12 ms 11 ms 12 ms hc-c76r1.router.hinet.net [168.95.90.98]
3 11 ms 11 ms 12 ms hc-c12r1.router.hinet.net [211.22.38.82]
4 15 ms 15 ms 15 ms tp-crs11.router.hinet.net [220.128.1.34]
5 16 ms 16 ms 16 ms r03-s2.tp.hinet.net [220.128.3.253]
6 16 ms 17 ms 17 ms r01-s2.tp.hinet.net [220.128.3.42]
7 16 ms 16 ms 17 ms 203-75-135-38.HINET-IP.hinet.net [203.75.135.38]

8 15 ms 25 ms 15 ms 209.85.243.26
9 17 ms 16 ms 19 ms 209.85.243.23
10 17 ms 20 ms 30 ms 209.85.241.154
11 18 ms 17 ms 16 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
62chaokai
2010-05-18, 04:59 PM
話說我線路由 ZyXel MGS-3712C 改成 首特 AF-101R 設備 (多台)
前幾天 ZyXel 的電源燒掉 全部都斷線 外面訂單資料傳不進來損失慘重 (人在北部無法回去處理)
後來改成 AF-101R 多台施工人員說這樣比較安全
2M/2M專線還是保持在 MGS-3712 其餘都移出來接在 AF-101R

為免大家不懂什麼是AF-101R，我貼個圖給大家看看。

http://www.pczone.com.tw/attachment.php?attachmentid=20634&stc=1&d=1274173071

不用我解釋吧，看到圖就知道是什了。