【討論】[10/24]關於FTTB 連線品質《ms》





頁 : 1 [2] 3 4 5

intela32015
2006-10-25, 12:56 AM
我是希望我打錯電話....本來想說大家都是混口飯吃吃,把名字post出來不太好。今天就是打了這隻電話.......所以才有感而發,也許是我自已抱著一定ok沒問題的心理才會有這種失落感,因為我本來是想申請10m/10m,換成hinet是連4m/4m都不到,但我跟朋友講好了是這個錢,所以也不好意思追加,邱先生也有跟我講過我這邊有台固電話線路,但FBA就是很抱歉,所以我覺得不是他的問題。至於IDC嘛,可能是他比較熱心覺得這樣可以解決掉我的問題,當時我又在開會,所以也沒辨法談很久,他也不知道我這邊的狀況。不過這只是個參考的案件。看看就好也不用太在意什麼。只能講固網只是集資撈錢的晃子罷了。

你的狀況跟我當時很像

這裡也沒光纖,甚至連台固電話線都沒有
結果後來還是裝了

現在10M都不能拉FBA的原因應該幾個月前台固開始限制
"該點要達到1萬5以上的收入才能拉光纖過去"




davidzyx
2006-10-25, 01:32 AM
5路經濟型,非固定ip.

Microsoft Windows XP [版本 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 168.95.1.1

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=5ms TTL=244
Reply from 168.95.1.1: bytes=32 time=5ms TTL=244
Reply from 168.95.1.1: bytes=32 time=5ms TTL=244
Reply from 168.95.1.1: bytes=32 time=5ms TTL=244

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

C:\Documents and Settings\Administrator>ping 168.95.192.1

Pinging 168.95.192.1 with 32 bytes of data:

Reply from 168.95.192.1: bytes=32 time=10ms TTL=244
Reply from 168.95.192.1: bytes=32 time=10ms TTL=244
Reply from 168.95.192.1: bytes=32 time=10ms TTL=244
Reply from 168.95.192.1: bytes=32 time=10ms TTL=244

Ping statistics for 168.95.192.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms

C:\Documents and Settings\Administrator>ping www.hinet.net

Pinging www.hinet.net [61.219.38.89] with 32 bytes of data:

Reply from 61.219.38.89: bytes=32 time=5ms TTL=246
Reply from 61.219.38.89: bytes=32 time=5ms TTL=246
Reply from 61.219.38.89: bytes=32 time=5ms TTL=246
Reply from 61.219.38.89: bytes=32 time=5ms TTL=246

Ping statistics for 61.219.38.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms

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

Pinging vip1.tw.tpe.yahoo.com [202.43.195.52] with 32 bytes of data:

Reply from 202.43.195.52: bytes=32 time=11ms TTL=54
Reply from 202.43.195.52: bytes=32 time=11ms TTL=54
Reply from 202.43.195.52: bytes=32 time=11ms TTL=54
Reply from 202.43.195.52: bytes=32 time=11ms TTL=54

Ping statistics for 202.43.195.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms

C:\Documents and Settings\Administrator>ping www.seed.net.tw

Pinging www.seed.net.tw [192.72.80.36] with 32 bytes of data:

Reply from 192.72.80.36: bytes=32 time=11ms TTL=241
Reply from 192.72.80.36: bytes=32 time=10ms TTL=241
Reply from 192.72.80.36: bytes=32 time=10ms TTL=241
Reply from 192.72.80.36: bytes=32 time=12ms TTL=241

Ping statistics for 192.72.80.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 10ms

C:\Documents and Settings\Administrator>ping www.apol.com.tw

Pinging www.apol.com.tw [203.79.224.100] with 32 bytes of data:

Reply from 203.79.224.100: bytes=32 time=9ms TTL=50
Reply from 203.79.224.100: bytes=32 time=9ms TTL=50
Reply from 203.79.224.100: bytes=32 time=9ms TTL=50
Reply from 203.79.224.100: bytes=32 time=9ms TTL=50

Ping statistics for 203.79.224.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms

C:\Documents and Settings\Administrator>ping www.giga.net.tw

Pinging www.giga.net.tw [203.133.0.185] with 32 bytes of data:

Reply from 203.133.0.185: bytes=32 time=9ms TTL=113
Reply from 203.133.0.185: bytes=32 time=8ms TTL=113
Reply from 203.133.0.185: bytes=32 time=7ms TTL=113
Reply from 203.133.0.185: bytes=32 time=7ms TTL=113

Ping statistics for 203.133.0.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 7ms

C:\Documents and Settings\Administrator>

extra-lan
2006-10-25, 06:15 AM
目前台灣光纖你要找到那麼低的ms只有兩個

台固
中華電信

************
************
還有新店的億聯光纖
ping time在4ms左右

gsg9
2006-10-25, 09:50 AM
ping time在4ms左右

給extra-lan,沒圖沒真相

但感謝大大們抽空回答。

hao0708
2006-10-25, 09:52 AM
目前台灣光纖你要找到那麼低的ms只有兩個

台固
中華電信

************
************
還有新店的億聯光纖
ping time在4ms左右


要做代業 提出點牛肉
請避免用簡單文字敘述

邱國彥
2006-10-26, 07:09 PM
Hi,好久沒來這裡啦!看到有關我個人的評論,唉!對開板的大大真的很抱歉想當初,INTELLA兄家裡也是10幾公里阿,台固花了大概110萬拉線,也是拉給他用,還雙路由備援喔!左邊10公里,右邊8公里!當初的評估是左右兩路只要有一路小於10公里,就不計算額外成本。現在,唉!500公尺啦!超過都要算,開板大大,我就算幫你送件評估,應該也是不會過,所以才建議您把機器放機房或是放INTELLA兄家,或是台北有另一個網友在數位通機房的機櫃也有空間,這兩個點都有台固光纖,可隨時提供!他們位在需要在開機或是簡單障礙排除也都可支援你,要不然真的沒招了。

swr
2006-10-26, 09:18 PM
Hi,好久沒來這裡啦!看到有關我個人的評論,唉!對開板的大大真的很抱歉想當初,INTELLA兄家裡也是10幾公里阿,台固花了大概110萬拉線,也是拉給他用,還雙路由備援喔!左邊10公里,右邊8公里!當初的評估是左右兩路只要有一路小於10公里,就不計算額外成本。現在,唉!500公尺啦!超過都要算,開板大大,我就算幫你送件評估,應該也是不會過,所以才建議您把機器放機房或是放INTELLA兄家,或是台北有另一個網友在數位通機房的機櫃也有空間,這兩個點都有台固光纖,可隨時提供!他們位在需要在開機或是簡單障礙排除也都可支援你,要不然真的沒招了。

沒辨法的事,不過說來台固連大陸的品質是比中華電信好
這也是為什麼有點小堅持要台固的FBA,不過人生嘛,不被打槍就不叫人生了。
現在只剩中華電信一家了,沒任何對手,這想想,也是算國內固網蠻可悲的地方。
不過我相信台灣固網遲早也會把光纖拉到這邊來的,因為至少高雄科學園區的餅應該還蠻大的。

extra-lan
2006-10-27, 11:32 AM
要做代業 提出點牛肉
請避免用簡單文字敘述

我只是想說明先前留言是講一個實際狀況
並不是要做廣告
不過我還是提供以下ping test的數據
以下是以億聯光纖寬頻2M/2M測試的結果

C:\Documents and Settings>ping 168.95.1.1

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=4ms TTL=241
Reply from 168.95.1.1: bytes=32 time=4ms TTL=241
Reply from 168.95.1.1: bytes=32 time=3ms TTL=241
Reply from 168.95.1.1: bytes=32 time=3ms TTL=241

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

C:\Documents and Settings>ping www.hinet.net

Pinging www.hinet.net [203.66.88.89] with 32 bytes of data:

Reply from 203.66.88.89: bytes=32 time=3ms TTL=243
Reply from 203.66.88.89: bytes=32 time=3ms TTL=243
Reply from 203.66.88.89: bytes=32 time=4ms TTL=243
Reply from 203.66.88.89: bytes=32 time=3ms TTL=243

Ping statistics for 203.66.88.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4ms, Average = 3ms

C:\Documents and Settings>ping tw.yahoo.com

Pinging w1.tw.vip.tpc.yahoo.com [203.84.202.164] with 32 bytes of data

Reply from 203.84.202.164: bytes=32 time=3ms TTL=55
Reply from 203.84.202.164: bytes=32 time=3ms TTL=55
Reply from 203.84.202.164: bytes=32 time=3ms TTL=55
Reply from 203.84.202.164: bytes=32 time=2ms TTL=55

Ping statistics for 203.84.202.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\Documents and Settings>ping www.seed.net.tw

Pinging www.seed.net.tw [192.72.80.36] with 32 bytes of data:

Reply from 192.72.80.36: bytes=32 time=2ms TTL=249
Reply from 192.72.80.36: bytes=32 time=2ms TTL=249
Reply from 192.72.80.36: bytes=32 time=2ms TTL=249
Reply from 192.72.80.36: bytes=32 time=3ms TTL=249

Ping statistics for 192.72.80.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\Documents and Settings>ping www.apol.com.tw

Pinging www.apol.com.tw [203.79.224.100] with 32 bytes of data:

Reply from 203.79.224.100: bytes=32 time=2ms TTL=55
Reply from 203.79.224.100: bytes=32 time=2ms TTL=55
Reply from 203.79.224.100: bytes=32 time=2ms TTL=55
Reply from 203.79.224.100: bytes=32 time=2ms TTL=55

Ping statistics for 203.79.224.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Documents and Settings>ping www.giga.net.tw

Pinging www.giga.net.tw [203.133.0.185] with 32 bytes of data:

Reply from 203.133.0.185: bytes=32 time=3ms TTL=123
Reply from 203.133.0.185: bytes=32 time=5ms TTL=123
Reply from 203.133.0.185: bytes=32 time=3ms TTL=123
Reply from 203.133.0.185: bytes=32 time=5ms TTL=123

Ping statistics for 203.133.0.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 5ms, Average = 4ms

C:\Documents and Settings>

黃志均
2006-10-27, 12:02 PM
Hi,好久沒來這裡啦!看到有關我個人的評論,唉!對開板的大大真的很抱歉想當初,INTELLA兄家裡也是10幾公里阿,台固花了大概110萬拉線,也是拉給他用,還雙路由備援喔!左邊10公里,右邊8公里!當初的評估是左右兩路只要有一路小於10公里,就不計算額外成本。現在,唉!500公尺啦!超過都要算,開板大大,我就算幫你送件評估,應該也是不會過,所以才建議您把機器放機房或是放INTELLA兄家,或是台北有另一個網友在數位通機房的機櫃也有空間,這兩個點都有台固光纖,可隨時提供!他們位在需要在開機或是簡單障礙排除也都可支援你,要不然真的沒招了。

我當初也是曾經與您聯繫,因為我自家用台固ADSL已經已經超過四五年了,為此年初朋友公司要拉光纖,我不但慫恿朋友力阻被HINET通吃,還配合貴公司營運範圍讓他說服老闆將線拉到該朋友家中當機房,當時並沒有公布說單點要一萬五以上(但單點也已經10M/10M每月近萬元,又是公司用頻寬不會亂搞),而且該點又是一個規模不小的社區,有心開發一定可以的。

但是幾次聯繫後我和朋友都放棄了,也深懷疑除中華電信外,其他固網根本沒有心思在與中華電信抗衡,或想要投資這塊市場,連生意送上門也都只考量立即的成本效益,這件事弄到最後我和朋友被主管罵死,只好連絡中華電信,沒多久就完成,相同價錢只拉了2M/2M,但送一條10M/2M。

這次事件讓我總算看清在台灣中華電信一定獨大的局面,當初可以推說電話線和最後一哩的問題,但現在光纖鋪建,中華電信如此積極,屆時光纖時代中華電信又是市場9成以上時,其他固網還有什麼臉找藉口?

這次事件我真的認真考慮換調台灣固網,反正短時間中華電信光纖到我那的機會遠遠大於其他固網,當初想力挺其他固網與中華抗衡,讓民眾有更多選擇的心思已蕩然無存,這種悲哀大概只有少許人可以體會吧......

黃志均
2006-10-27, 01:26 PM
就像現在我上班的這棟住辦大樓
日前我藉由機會已經向主委建議拉光纖進來
對不起,要是以前我一定會先聯繫民營固網
這一次我完全不考量
因為「單點不到一萬五」

可是你知道嗎,這棟樓七、八十戶中
有約50戶現在在使用ADSL
平均月費均超過千元
而且私下了解,不到一成多會堅持非HINET不可
但是當中華電信+HINET拉光纖進來
這些用戶預計超過9成會更換成使用HINET光纖
而且其中不乏非HINET用戶
如果保守以35戶計算
每月超過一萬五是沒有問題

這就是民營固網最大的危機
只做短視的獲利規劃
哪知早已經奠下敗筆
等著日後自品苦果

當然,我們這些使用者也同樣面臨未來市場獨佔的苦果
但是令人氣憤短視的民營固網
我們還能有什麼期盼?