線路問題集中討論

[Rena]

和寵物交配有關嗎？有人在做交配嗎？

[hiphopsicfuret]

GM大大~ 辛苦了 / \

[GM Godzilla]

伺服器已經恢復正常，各位可以登入遊戲了！！

[GM Judas]

Dears,
目前正聯繫管理伺服器的GM中，請大家稍等。
Thanks!

[ymca1234]

很久沒當了
是時候當一次機 休息

[hiphopsicfuret]

現在連不上???? 只有我這樣嗎O O?

[ymca1234]

是!! 當了機

[sobo]

時間十一點整左右。

[Cipher]

基本上不算 lag, 根據經驗會出現 time out 的地方有兩點:

1. 第 15 個 route 海外連到 Hinet 的那一段
2. 最後一個連到主機的 route (應該是指 Server 本身).

Ping statistics for 122.116.138.145:
Packets: Sent = 324, Received = 323, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 283ms, Average = 199ms

後期關站前用雙向 512 從海外走"一步"要三秒, 現在可以玩已經偷笑了.

Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 * 2 ms 1 ms x.x.x.x
2 12 ms 8 ms 9 ms 10.88.16.1
3 10 ms 16 ms 10 ms xxx01xxxca-gbe-1-34.charter.com [96.34.97.xxx]
4 9 ms 19 ms 7 ms 96-34-96-22.static.unas.ca.charter.com [96.34.96.22]
5 13 ms 12 ms 11 ms bbr01mtpkca-tge-0-0-0-6.mtpk.ca.charter.com [96.34.2.24]
6 9 ms 11 ms 10 ms los-edge-01.inet.qwest.net [208.46.190.193]
7 23 ms 9 ms 11 ms los-core-02.inet.qwest.net [205.171.32.37]
8 11 ms 10 ms 12 ms lap-brdr-01.inet.qwest.net [205.171.32.14]
9 22 ms 15 ms 12 ms 0.so-5-0-0.BR1.LAX7.ALTER.NET [204.255.168.33]
10 14 ms 13 ms 12 ms 0.so-6-0-0.XT2.LAX7.ALTER.NET [152.63.112.154]
11 28 ms 21 ms 21 ms 0.so-4-0-0.XL2.PAO1.ALTER.NET [152.63.54.82]
12 23 ms 27 ms 22 ms POS5-0.IG2.PAO1.ALTER.NET [152.63.49.137]
13 37 ms 22 ms 29 ms chunghwa-gw.customer.alter.net [63.65.131.122]
14 28 ms 35 ms 23 ms r02-pa.us.hinet.net [202.39.83.1]
15 159 ms 157 ms 153 ms r02-s2.tp.hinet.net [211.72.108.206]
16 157 ms 163 ms 154 ms 220-128-7-130.HINET-IP.hinet.net [220.128.7.130]
17 170 ms 191 ms 167 ms 220-128-7-174.HINET-IP.hinet.net [220.128.7.174]
18 173 ms 170 ms 175 ms tp-pc1-t64-1.router.hinet.net [220.128.2.53]
19 174 ms 171 ms 170 ms h105.s75.ts.hinet.net [168.95.75.105]
20 220 ms 203 ms 202 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.145]

Trace complete.

[S.H.E.]

昨天上線明顯比之前順得多, 不知其他香港玩家是否一樣.

[布拉價]

請台灣的玩家報告一下lag的情況

另外，建議用tracert去看哪個節點出問題
在windows命令列下打 tracert login.odyes.com

報告: 台灣地區目前很順暢!!

[GM Aron]

請台灣的玩家報告一下lag的情況

另外，建議用tracert去看哪個節點出問題
在windows命令列下打 tracert login.odyes.com

[GM YesMaster]

其它玩家是否也會lag
因主機在台灣所以無法保證
從其它地方連過來不會lag

[Rena]

shanghai：2月23日晚10點測

之前晚上一般100左右，現在150左右，還有time out

Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:

Reply from 122.116.138.145: bytes=32 time=173ms TTL=115
Reply from 122.116.138.145: bytes=32 time=154ms TTL=115
Reply from 122.116.138.145: bytes=32 time=163ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=158ms TTL=115
Reply from 122.116.138.145: bytes=32 time=145ms TTL=115
Reply from 122.116.138.145: bytes=32 time=138ms TTL=115
Reply from 122.116.138.145: bytes=32 time=149ms TTL=115
Reply from 122.116.138.145: bytes=32 time=151ms TTL=115
Reply from 122.116.138.145: bytes=32 time=153ms TTL=115
Reply from 122.116.138.145: bytes=32 time=146ms TTL=115
Reply from 122.116.138.145: bytes=32 time=150ms TTL=115
Reply from 122.116.138.145: bytes=32 time=150ms TTL=115
Reply from 122.116.138.145: bytes=32 time=154ms TTL=115
Reply from 122.116.138.145: bytes=32 time=137ms TTL=115
Reply from 122.116.138.145: bytes=32 time=145ms TTL=115
Reply from 122.116.138.145: bytes=32 time=144ms TTL=115
Reply from 122.116.138.145: bytes=32 time=149ms TTL=115
Reply from 122.116.138.145: bytes=32 time=156ms TTL=115
Reply from 122.116.138.145: bytes=32 time=155ms TTL=115
Reply from 122.116.138.145: bytes=32 time=153ms TTL=115
Reply from 122.116.138.145: bytes=32 time=153ms TTL=115
Reply from 122.116.138.145: bytes=32 time=150ms TTL=115
Reply from 122.116.138.145: bytes=32 time=144ms TTL=115
Reply from 122.116.138.145: bytes=32 time=145ms TTL=115
Reply from 122.116.138.145: bytes=32 time=152ms TTL=115
Reply from 122.116.138.145: bytes=32 time=149ms TTL=115
Reply from 122.116.138.145: bytes=32 time=140ms TTL=115
Reply from 122.116.138.145: bytes=32 time=158ms TTL=115
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=147ms TTL=115
Reply from 122.116.138.145: bytes=32 time=155ms TTL=115
Reply from 122.116.138.145: bytes=32 time=152ms TTL=115
Reply from 122.116.138.145: bytes=32 time=155ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=157ms TTL=115
Reply from 122.116.138.145: bytes=32 time=166ms TTL=115
Reply from 122.116.138.145: bytes=32 time=164ms TTL=115
Reply from 122.116.138.145: bytes=32 time=162ms TTL=115
Reply from 122.116.138.145: bytes=32 time=168ms TTL=115
Reply from 122.116.138.145: bytes=32 time=167ms TTL=115
Request timed out.
Reply from 122.116.138.145: bytes=32 time=172ms TTL=115
Reply from 122.116.138.145: bytes=32 time=160ms TTL=115
Reply from 122.116.138.145: bytes=32 time=153ms TTL=115
Reply from 122.116.138.145: bytes=32 time=172ms TTL=115
Reply from 122.116.138.145: bytes=32 time=180ms TTL=115
Reply from 122.116.138.145: bytes=32 time=172ms TTL=115
Reply from 122.116.138.145: bytes=32 time=153ms TTL=115
Reply from 122.116.138.145: bytes=32 time=147ms TTL=115
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=166ms TTL=115
Reply from 122.116.138.145: bytes=32 time=152ms TTL=115
Reply from 122.116.138.145: bytes=32 time=158ms TTL=115
Reply from 122.116.138.145: bytes=32 time=155ms TTL=115
Reply from 122.116.138.145: bytes=32 time=162ms TTL=115
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=163ms TTL=115
Reply from 122.116.138.145: bytes=32 time=162ms TTL=115
Reply from 122.116.138.145: bytes=32 time=159ms TTL=115
Reply from 122.116.138.145: bytes=32 time=170ms TTL=115
Reply from 122.116.138.145: bytes=32 time=156ms TTL=115
Reply from 122.116.138.145: bytes=32 time=147ms TTL=115
Reply from 122.116.138.145: bytes=32 time=165ms TTL=115
Reply from 122.116.138.145: bytes=32 time=155ms TTL=115
Reply from 122.116.138.145: bytes=32 time=154ms TTL=115
Reply from 122.116.138.145: bytes=32 time=169ms TTL=115
Reply from 122.116.138.145: bytes=32 time=178ms TTL=115
Reply from 122.116.138.145: bytes=32 time=166ms TTL=115
Reply from 122.116.138.145: bytes=32 time=170ms TTL=115
Reply from 122.116.138.145: bytes=32 time=168ms TTL=115

Ping statistics for 122.116.138.145:
Packets: Sent = 73, Received = 70, Lost = 3 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 180ms, Average = 156ms

[GM YesMaster]

管理的GM最近未上線
不敢冒然重新啟動Server...