HiNet 爆炸
2007-09-15 01:50
我家的 ADSL ,
到 GW 還正常 , 再出去一個點就掉封包掉得好慘 ......
打 123 去問
客服人員說機房斷線 正在處理中 ....
正在苦惱那我怎麼工作時 ....
突然想起 我有備援線路啊 !!
拿出 3G網卡 裝上 繼續工作 .... ccc
$ traceroute -n 168.95.1.1
traceroute to 168.95.1.1 (168.95.1.1), 30 hops max, 40 byte packets
1 61.217.32.254 38.907 ms 38.609 ms 39.671 ms
2 168.95.101.82 36.907 ms 37.944 ms 37.924 ms
3 211.22.36.42 37.887 ms 211.22.36.182 36.938 ms 211.22.36.42 36.925 ms
4 * 220.128.2.234 38.143 ms 220.128.1.234 39.044 ms
5 220.128.2.233 38.408 ms * 38.580 ms
6 * 211.22.34.214 37.377 ms 37.924 ms
7 211.22.35.53 37.956 ms 37.914 ms 37.966 ms
8 210.59.204.194 38.360 ms * *
9 210.59.204.202 38.521 ms 38.443 ms 37.903 ms
==============================================================================
$ sudo ./ping2.pl -p icmp -c 50 -i 0.1 -w 0.1 61.217.32.254
Pinging 61.217.32.254 with 32 bytes of data(icmp):
1: Reply from 61.217.32.254: time=39.58 ms
2: Reply from 61.217.32.254: time=41.98 ms
3: Reply from 61.217.32.254: time=40.98 ms
4: Reply from 61.217.32.254: time=43.99 ms
5: Reply from 61.217.32.254: time=39.35 ms
6: Reply from 61.217.32.254: time=39.00 ms
7: Reply from 61.217.32.254: time=39.93 ms
8: Reply from 61.217.32.254: time=39.96 ms
9: Reply from 61.217.32.254: time=38.92 ms
10: Reply from 61.217.32.254: time=39.97 ms
11: Reply from 61.217.32.254: time=39.89 ms
12: Reply from 61.217.32.254: time=38.97 ms
13: Reply from 61.217.32.254: time=39.91 ms
14: Reply from 61.217.32.254: time=39.90 ms
15: Reply from 61.217.32.254: time=39.48 ms
16: Reply from 61.217.32.254: time=40.88 ms
17: Reply from 61.217.32.254: time=48.89 ms
18: Reply from 61.217.32.254: time=39.90 ms
19: Reply from 61.217.32.254: time=40.31 ms
20: Reply from 61.217.32.254: time=39.89 ms
21: Reply from 61.217.32.254: time=40.84 ms
22: Reply from 61.217.32.254: time=40.84 ms
23: Reply from 61.217.32.254: time=52.88 ms
24: Reply from 61.217.32.254: time=41.85 ms
25: Reply from 61.217.32.254: time=39.87 ms
26: Reply from 61.217.32.254: time=40.87 ms
27: Reply from 61.217.32.254: time=39.93 ms
28: Reply from 61.217.32.254: time=40.85 ms
29: Reply from 61.217.32.254: time=41.76 ms
30: Reply from 61.217.32.254: time=39.80 ms
31: Reply from 61.217.32.254: time=41.81 ms
32: Reply from 61.217.32.254: time=39.82 ms
33: Reply from 61.217.32.254: time=40.21 ms
34: Reply from 61.217.32.254: time=43.32 ms
35: Reply from 61.217.32.254: time=40.80 ms
36: Reply from 61.217.32.254: time=39.81 ms
37: Reply from 61.217.32.254: time=44.82 ms
38: Reply from 61.217.32.254: time=39.87 ms
39: Reply from 61.217.32.254: time=39.78 ms
40: Reply from 61.217.32.254: time=39.81 ms
41: Reply from 61.217.32.254: time=39.74 ms
42: Reply from 61.217.32.254: time=39.79 ms
43: Reply from 61.217.32.254: time=39.76 ms
44: Reply from 61.217.32.254: time=54.78 ms
45: Reply from 61.217.32.254: time=39.73 ms
46: Reply from 61.217.32.254: time=41.75 ms
47: Reply from 61.217.32.254: time=40.11 ms
48: Reply from 61.217.32.254: time=39.72 ms
49: Reply from 61.217.32.254: time=53.74 ms
50: Reply from 61.217.32.254: time=40.71 ms
Ping statistics for 61.217.32.254 :
Packets: Sent = 50, Received = 50, Lost = 0 ( 0.00% loss ),
Approximate round trip times in milli-seconds:
Minimum = 38.92 ms, Maximum = 54.78 ms, Average = 41.42 ms
==============================================================================
$ sudo ./ping2.pl -p icmp -c 50 -i 0.1 -w 0.1 168.95.101.82
Pinging 168.95.101.82 with 32 bytes of data(tcp):
1: Request timed out.
2: Request timed out.
3: Reply from 168.95.101.82: time=39.21 ms
4: Request timed out.
5: Reply from 168.95.101.82: time=39.96 ms
6: Request timed out.
7: Request timed out.
8: Reply from 168.95.101.82: time=39.33 ms
9: Request timed out.
10: Request timed out.
11: Reply from 168.95.101.82: time=38.98 ms
12: Request timed out.
13: Request timed out.
14: Request timed out.
15: Reply from 168.95.101.82: time=38.89 ms
16: Reply from 168.95.101.82: time=39.92 ms
17: Reply from 168.95.101.82: time=38.91 ms
18: Reply from 168.95.101.82: time=38.93 ms
19: Request timed out.
20: Request timed out.
21: Reply from 168.95.101.82: time=38.87 ms
22: Request timed out.
23: Reply from 168.95.101.82: time=38.86 ms
24: Reply from 168.95.101.82: time=38.80 ms
25: Request timed out.
26: Reply from 168.95.101.82: time=38.91 ms
27: Reply from 168.95.101.82: time=38.86 ms
28: Reply from 168.95.101.82: time=39.41 ms
29: Request timed out.
30: Request timed out.
31: Reply from 168.95.101.82: time=39.84 ms
32: Request timed out.
33: Reply from 168.95.101.82: time=38.84 ms
34: Request timed out.
35: Reply from 168.95.101.82: time=38.83 ms
36: Request timed out.
37: Reply from 168.95.101.82: time=38.62 ms
38: Request timed out.
39: Reply from 168.95.101.82: time=38.80 ms
40: Request timed out.
41: Reply from 168.95.101.82: time=48.72 ms
42: Reply from 168.95.101.82: time=38.78 ms
43: Reply from 168.95.101.82: time=38.59 ms
44: Request timed out.
45: Reply from 168.95.101.82: time=38.76 ms
46: Request timed out.
47: Request timed out.
48: Request timed out.
49: Reply from 168.95.101.82: time=39.07 ms
50: Request timed out.
Ping statistics for 168.95.101.82 :
Packets: Sent = 50, Received = 24, Lost = 26 ( 52% loss ),
Approximate round trip times in milli-seconds:
Minimum = 38.59 ms, Maximum = 48.72 ms, Average = 39.45 ms
HIT 資安技術教育訓練課程 與 Syscan in Taipei 2007FTTB
新增留言
訂閱這則留言的 RSS Feed