裝 ipfilter 有什麼用？

ipfilter 的用處是將一些反 P2P 組織、政府機關、電影公司、唱片公司等等的 ip 作阻擋，而不與這些 ip 作資料上的傳輸，跟 isp 限速 p2p 一點關係也沒有，如果用了會變快的話應該是你的幻覺吧。

贊助商連結

測試剛才的熱門檔之後
裝完後與裝完前
裝完後速度比之前沒裝慢了點(大部分是下降很多) 連種的數量與連結數似乎降低了些
奇怪的是速度比裝前穩定一點 不會有大幅上下跳動
可能唯一只有這點是好的
應該沒有影響　裝完之後還會有反效果　
電腦王那種不求證沒有大量測試的實驗所提出的小道消息（大部分都是網路上看人盜聽塗說不求甚解下隨意抄來寫槁子）　
你能覺得它百分之百有用嗎？？　

基本上只要so-net有執行運作擋bt＆ed的機器　
這種小手段幾乎沒什屁用　

我的219.84.***.** 真是欲哭無淚
so-net 的IP都是長個什麼樣的呢？
我看我的btcomet裡IP 是 219.80.***.** 或219.81.***.**
都好不到哪裡去

也許真的是幻覺...我的IP是61.64開頭的..小弟很幸運
昨晚從發文後到3日14:00共抓了7部1 支筆.每部都1.2GB 一直維持(160-170K因為我限速)
大家不要試好了...就看該死的sonet何時改進?

昨天還有今天我觀察 驢子上傳的結果
我發現 上傳會有時會不正常有時會正常(達到我的上傳設定)

so-net 有沒P2P限速用這個去測試便知道

http://dl4.www2.btchina.net/download.php?s=a19ea5b9962a3b48&attachmentid=461769

上百個種子，下載還會跌到個位數，你說呢？

不只P2P問題so-net甚至晚上連hinet 根本就抓不了東西
用Flashget也不能掛porxy一掛一定會出現404 看來so-net真的快爛了
被日本總公司聽到這種情況真不知作何感想

x的　今晚毛病又發作了（更！　 :mad: 　請問一下　這種毛病換ip可以解決嗎？）　
１、ping　hinet系網站的各ms值（有些竟然還會掉封包　更！）　
C:\Documents and Settings\xxxxxx>ping -n 20 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=289ms TTL=243
Reply from 203.66.88.89: bytes=32 time=301ms TTL=243
Reply from 203.66.88.89: bytes=32 time=310ms TTL=243
Reply from 203.66.88.89: bytes=32 time=285ms TTL=243
Reply from 203.66.88.89: bytes=32 time=279ms TTL=243
Reply from 203.66.88.89: bytes=32 time=286ms TTL=243
Reply from 203.66.88.89: bytes=32 time=290ms TTL=243
Reply from 203.66.88.89: bytes=32 time=285ms TTL=243
Reply from 203.66.88.89: bytes=32 time=285ms TTL=243
Reply from 203.66.88.89: bytes=32 time=285ms TTL=243
Reply from 203.66.88.89: bytes=32 time=297ms TTL=243
Reply from 203.66.88.89: bytes=32 time=298ms TTL=243
Reply from 203.66.88.89: bytes=32 time=298ms TTL=243
Reply from 203.66.88.89: bytes=32 time=296ms TTL=243
Reply from 203.66.88.89: bytes=32 time=290ms TTL=243
Reply from 203.66.88.89: bytes=32 time=293ms TTL=243
Reply from 203.66.88.89: bytes=32 time=281ms TTL=243
Reply from 203.66.88.89: bytes=32 time=277ms TTL=243
Reply from 203.66.88.89: bytes=32 time=279ms TTL=243
Reply from 203.66.88.89: bytes=32 time=280ms TTL=243

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

C:\Documents and Settings\xxxxxx>ping -n 20 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=293ms TTL=51
Reply from 202.43.195.52: bytes=32 time=296ms TTL=51
Reply from 202.43.195.52: bytes=32 time=288ms TTL=51
Reply from 202.43.195.52: bytes=32 time=285ms TTL=51
Reply from 202.43.195.52: bytes=32 time=283ms TTL=51
Reply from 202.43.195.52: bytes=32 time=293ms TTL=51
Reply from 202.43.195.52: bytes=32 time=283ms TTL=51
Reply from 202.43.195.52: bytes=32 time=287ms TTL=51
Reply from 202.43.195.52: bytes=32 time=292ms TTL=51
Reply from 202.43.195.52: bytes=32 time=291ms TTL=51
Reply from 202.43.195.52: bytes=32 time=282ms TTL=51
Reply from 202.43.195.52: bytes=32 time=282ms TTL=51
Reply from 202.43.195.52: bytes=32 time=278ms TTL=51
Reply from 202.43.195.52: bytes=32 time=271ms TTL=51
Reply from 202.43.195.52: bytes=32 time=266ms TTL=51
Reply from 202.43.195.52: bytes=32 time=275ms TTL=51
Reply from 202.43.195.52: bytes=32 time=274ms TTL=51
Reply from 202.43.195.52: bytes=32 time=282ms TTL=51
Reply from 202.43.195.52: bytes=32 time=290ms TTL=51
Reply from 202.43.195.52: bytes=32 time=296ms TTL=51

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

C:\Documents and Settings\xxxxxx>ping -n 20 www.pchome.com.tw

Pinging www.pchome.com.tw [210.59.230.60] with 32 bytes of data:

Reply from 210.59.230.60: bytes=32 time=302ms TTL=49
Reply from 210.59.230.60: bytes=32 time=298ms TTL=49
Reply from 210.59.230.60: bytes=32 time=303ms TTL=49
Reply from 210.59.230.60: bytes=32 time=307ms TTL=49
Reply from 210.59.230.60: bytes=32 time=307ms TTL=49
Reply from 210.59.230.60: bytes=32 time=292ms TTL=49
Reply from 210.59.230.60: bytes=32 time=295ms TTL=49
Reply from 210.59.230.60: bytes=32 time=296ms TTL=49
Reply from 210.59.230.60: bytes=32 time=282ms TTL=49
Reply from 210.59.230.60: bytes=32 time=283ms TTL=49
Reply from 210.59.230.60: bytes=32 time=282ms TTL=49
Reply from 210.59.230.60: bytes=32 time=278ms TTL=49
Reply from 210.59.230.60: bytes=32 time=284ms TTL=49
Reply from 210.59.230.60: bytes=32 time=272ms TTL=49
Reply from 210.59.230.60: bytes=32 time=265ms TTL=49
Reply from 210.59.230.60: bytes=32 time=270ms TTL=49
Reply from 210.59.230.60: bytes=32 time=275ms TTL=49
Reply from 210.59.230.60: bytes=32 time=277ms TTL=49
Reply from 210.59.230.60: bytes=32 time=278ms TTL=49
Request timed out.

Ping statistics for 210.59.230.60:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 307ms, Average = 286ms　

C:\Documents and Settings\xxxxxx>ping -n 20 www.chinatimes.com.tw

Pinging www.chinatimes.com [210.65.0.10] with 32 bytes of data:

Reply from 210.65.0.10: bytes=32 time=343ms TTL=243
Reply from 210.65.0.10: bytes=32 time=292ms TTL=243
Reply from 210.65.0.10: bytes=32 time=379ms TTL=243
Reply from 210.65.0.10: bytes=32 time=332ms TTL=243
Reply from 210.65.0.10: bytes=32 time=311ms TTL=243
Reply from 210.65.0.10: bytes=32 time=320ms TTL=243
Reply from 210.65.0.10: bytes=32 time=318ms TTL=243
Reply from 210.65.0.10: bytes=32 time=319ms TTL=243
Reply from 210.65.0.10: bytes=32 time=323ms TTL=243
Reply from 210.65.0.10: bytes=32 time=333ms TTL=243
Reply from 210.65.0.10: bytes=32 time=375ms TTL=243
Request timed out.
Reply from 210.65.0.10: bytes=32 time=308ms TTL=243
Reply from 210.65.0.10: bytes=32 time=342ms TTL=243
Reply from 210.65.0.10: bytes=32 time=334ms TTL=243
Reply from 210.65.0.10: bytes=32 time=332ms TTL=243
Reply from 210.65.0.10: bytes=32 time=305ms TTL=243
Reply from 210.65.0.10: bytes=32 time=306ms TTL=243
Reply from 210.65.0.10: bytes=32 time=300ms TTL=243
Reply from 210.65.0.10: bytes=32 time=296ms TTL=243

Ping statistics for 210.65.0.10:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 292ms, Maximum = 379ms, Average = 324ms

２、ping seednet系網站的ms值（幸好不像hinet :( 　不過也慢了些）　
C:\Documents and Settings\xxxxxx>ping -n 20 www.gamer.com.tw

Pinging www.gamer.com.tw [210.64.125.13] with 32 bytes of data:

Reply from 210.64.125.13: bytes=32 time=56ms TTL=57
Reply from 210.64.125.13: bytes=32 time=50ms TTL=57
Reply from 210.64.125.13: bytes=32 time=57ms TTL=57
Reply from 210.64.125.13: bytes=32 time=74ms TTL=57
Reply from 210.64.125.13: bytes=32 time=63ms TTL=57
Reply from 210.64.125.13: bytes=32 time=52ms TTL=57
Reply from 210.64.125.13: bytes=32 time=78ms TTL=57
Reply from 210.64.125.13: bytes=32 time=63ms TTL=57
Reply from 210.64.125.13: bytes=32 time=78ms TTL=57
Reply from 210.64.125.13: bytes=32 time=76ms TTL=57
Reply from 210.64.125.13: bytes=32 time=75ms TTL=57
Reply from 210.64.125.13: bytes=32 time=58ms TTL=57
Request timed out.
Reply from 210.64.125.13: bytes=32 time=74ms TTL=57
Reply from 210.64.125.13: bytes=32 time=80ms TTL=57
Reply from 210.64.125.13: bytes=32 time=64ms TTL=57
Reply from 210.64.125.13: bytes=32 time=77ms TTL=57
Reply from 210.64.125.13: bytes=32 time=53ms TTL=57
Reply from 210.64.125.13: bytes=32 time=55ms TTL=57
Reply from 210.64.125.13: bytes=32 time=76ms TTL=57

Ping statistics for 210.64.125.13:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 80ms, Average = 66ms　

３、餿net 自家的ping值（如果慢　那就可以關門大吉　正常值）　
C:\Documents and Settings\xxxxxx>ping -n 20 www.so-net.net.tw

Pinging www.so-net.net.tw [61.64.127.7] with 32 bytes of data:

Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=49ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=48ms TTL=249
Reply from 61.64.127.7: bytes=32 time=48ms TTL=249
Reply from 61.64.127.7: bytes=32 time=47ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=51ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=49ms TTL=249
Reply from 61.64.127.7: bytes=32 time=47ms TTL=249
Reply from 61.64.127.7: bytes=32 time=49ms TTL=249
Reply from 61.64.127.7: bytes=32 time=47ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=50ms TTL=249
Reply from 61.64.127.7: bytes=32 time=49ms TTL=249
Reply from 61.64.127.7: bytes=32 time=48ms TTL=249

Ping statistics for 61.64.127.7:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 51ms, Average = 49ms

學網ftp&http下載均正常

不只P2P問題so-net甚至晚上連hinet 根本就抓不了東西
用Flashget也不能掛porxy一掛一定會出現404 看來so-net真的快爛了
被日本總公司聽到這種情況真不知作何感想

想問一下　那個網址有hinet的檔案可以方便下載測試的　

還有一問是之前就想問的　
就是so-net固定ip（我是剛裝不到半個月的新客戶）　
可以掛proxy嗎（我測試過掛hinet的與之前常用的外國proxy都不能用　設定之後連不上任何網站)　
是官方已限定不能用了　
還是只有固定ip不能用　浮動制能用呢？　
請知情的人幫忙回答一下

每次出問題 好像常常都在禮拜3發生