| 苦命人  | HINET固3光纖的慘狀 時間:2008年7月30日晚上8點半 確認過當時使用頻寬 下載1.5-2M之間/上傳約512K上下 遠端PING GW 220.128.131.254正常 遠端PING路由器的結果: Reply from 220.128.131.67: bytes=32 time=1606ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1645ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1309ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1298ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1186ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1425ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1506ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1330ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1286ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1382ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1289ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1263ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1247ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1235ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1397ms TTL=58 Request timed out. Reply from 220.128.131.67: bytes=32 time=1193ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1470ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1406ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1458ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1757ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1648ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1539ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1676ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1544ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1649ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1431ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1329ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1438ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1534ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1485ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1341ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1282ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1379ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1350ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1229ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1172ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1242ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1000ms TTL=58 Reply from 220.128.131.67: bytes=32 time=1059ms TTL=58 Reply from 220.128.131.67: bytes=32 time=645ms TTL=58 Reply from 220.128.131.67: bytes=32 time=937ms TTL=58 還有更慘的狀況,太長不貼了 等報修結果出來再說 此篇文章於 2008-07-30 09:03 PM 被 acion 編輯。. |
| 回覆 |
| 會員  | 回覆: HINET固3光纖的慘狀 目前 7/30 10:27 PM 我從 北健 Ping 你的 IP 結果： Reply from 220.128.131.67: bytes=32 time=48ms TTL=48 Reply from 220.128.131.67: bytes=32 time=38ms TTL=48 Reply from 220.128.131.67: bytes=32 time=27ms TTL=48 Reply from 220.128.131.67: bytes=32 time=30ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 Reply from 220.128.131.67: bytes=32 time=38ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 Reply from 220.128.131.67: bytes=32 time=31ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 Reply from 220.128.131.67: bytes=32 time=30ms TTL=48 Reply from 220.128.131.67: bytes=32 time=34ms TTL=48 Reply from 220.128.131.67: bytes=32 time=30ms TTL=48 Reply from 220.128.131.67: bytes=32 time=35ms TTL=48 Reply from 220.128.131.67: bytes=32 time=30ms TTL=48 Reply from 220.128.131.67: bytes=32 time=39ms TTL=48 Reply from 220.128.131.67: bytes=32 time=30ms TTL=48 Reply from 220.128.131.67: bytes=32 time=32ms TTL=48 Reply from 220.128.131.67: bytes=32 time=28ms TTL=48 從 HiNet 8M ADSL Ping : Reply from 220.128.131.67: bytes=32 time=49ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=55ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=52ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=49ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=49ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=49ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 Reply from 220.128.131.67: bytes=32 time=50ms TTL=56 你是從哪邊 Ping 你的 IP ？ |
| 回覆 |
| 嚴禁大濕暴走 | 回覆: HINET固3光纖的慘狀 有這麼慘?我看樓主要報修了。 我也有一條固3IP的CHT FTTB Pinging 220.128.131.67 with 32 bytes of data: Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=62ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=52ms TTL=53 Reply from 220.128.131.67: bytes=32 time=62ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=52ms TTL=53 Reply from 220.128.131.67: bytes=32 time=52ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=54ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=59ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=54ms TTL=53 Reply from 220.128.131.67: bytes=32 time=52ms TTL=53 Reply from 220.128.131.67: bytes=32 time=57ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=57ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=58ms TTL=53 Reply from 220.128.131.67: bytes=32 time=75ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=61ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=55ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=65ms TTL=53 Reply from 220.128.131.67: bytes=32 time=69ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=57ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=51ms TTL=53 Reply from 220.128.131.67: bytes=32 time=55ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=52ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 Reply from 220.128.131.67: bytes=32 time=49ms TTL=53 Reply from 220.128.131.67: bytes=32 time=53ms TTL=53 Reply from 220.128.131.67: bytes=32 time=50ms TTL=53 |
| 回覆 |
| 校長兼撞鐘  | 回覆: HINET固3光纖的慘狀 外部 ping 該 ip 都差不多在 2x ms acion 兄是在下載 & 上傳情況下 ping 的嗎？ 沒作任何網路運作的情況下作 ping 的測試又會是多少？ 進出的網路封包量真的很大量的情況下(bt?) 才會發生 ping 到 1xxxms & 掉封包吧 若是一般用途(www , ftp , game)下載 & 上傳時測試的 ping 值那麼爛 , 真的是要叫修了 |
| 回覆 |
| 苦命人 | 回覆: HINET固3光纖的慘狀 我有很多條hinet固3光纖(目前還有很多固3 adsl在邊用邊改接光纖中),所以是從其他一條遠端ping到有問題的那一條 站上大大偵測的狀況正常,是因為該路電路ping值飆高甚至中斷,是不定時出的狀況, 平時我遠端偵測(大概也只是偵測5到10分鐘)也都正常,是客戶反應遊戲延遲有一段時日,才決定連續ping一天看看,結果不到20分鐘狀況就出現了, 多年來hinet網路都沒問題且同地區其他路也都正常(與有問題的這一路不同用戶端電路),個人比較懷疑的是用戶端光纖電路頻寬不足,如果是的話,那麻煩就大了 客人當然會使用p2p之類的軟體,不過有限連線數,當時對外連線數不到800條 路由器是qno的4wan產品,多年來一大堆同型產品總共只當機過一次,沒出過開板的問題 此篇文章於 2008-07-31 10:04 AM 被 acion 編輯。. |
| 回覆 |
| 網咖C組  | 回覆: HINET固3光纖的慘狀 從對岸連都沒這麼慘 Reply from 220.128.131.67: bytes=32 time=160ms TTL=50 Reply from 220.128.131.67: bytes=32 time=166ms TTL=50 Reply from 220.128.131.67: bytes=32 time=146ms TTL=50 Reply from 220.128.131.67: bytes=32 time=142ms TTL=50 Reply from 220.128.131.67: bytes=32 time=146ms TTL=50 Reply from 220.128.131.67: bytes=32 time=151ms TTL=50 Reply from 220.128.131.67: bytes=32 time=180ms TTL=50 Reply from 220.128.131.67: bytes=32 time=171ms TTL=50 Reply from 220.128.131.67: bytes=32 time=174ms TTL=50 |
| 回覆 |
| 苦命人 | 回覆: HINET固3光纖的慘狀 剛剛3點半中華電信的維修工程師過來說 1.現在沒問題就代表沒問題, 2.遠端ping(有對比數據,有hinet給的mrtg流量圖)看都不看,一句話只認現場,其他不認帳 3.晚上尖峰時間會有問題,抱歉下班了,不管 4.要不然跟公司說不要租我們 有法定善意第三人在旁邊還這樣,真是夠囂張的了 此篇文章於 2008-07-31 03:42 PM 被 acion 編輯。. |
| 回覆 |
| 豬生廢猿 | 回覆: HINET固3光纖的慘狀 換別家吧! 先從ISP換起, 有FTTB 固3的又不只Hinet, 不是嗎? 哪天有別的固網的線路, 再連線路都換吧! |
| 回覆 |
| 會員  | 引用:
引用:
| ||
| 回覆 |
| 苦命人 | 回覆: HINET固3光纖的慘狀 引用:
以前接兩條固3 adsl現在改光纖所以只有一條 wan2.3.4全部關閉 同款路由器韌體都是最新版,其他地點都正常(用戶甚至多一倍不止) 有問題的這邊以前全部正常,是最近換光纖後才發生問題 | |
| 回覆 |
| XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見，並不代表本站之立場，討論區以「即時留言」方式運作，故無法完全監察所有即時留言，若您發現文章可能有異議，請 email :[email protected] 處理。
