1	01:35:35.317	'805239': connect failed [没有连接]
0	01:35:55.864	'805239': login on HTFXVULTD-Live through DC-1 (ping: 246.10 ms)
0	01:36:09.286	'805239': previous successful authorization performed from 152.32.128.46
0	01:36:16.473	'805239': auto connecting to a better access point DC-4 (ping is 230.85 ms)
0	01:36:17.114	'805239': login on HTFXVULTD-Live through DC-4 (ping: 230.85 ms)
0	01:36:18.926	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 230.85 ms)
0	01:36:19.551	'805239': previous successful authorization performed from 152.32.128.46
1	08:36:48.278	'805239': ping failed
1	08:36:48.278	'805239': datacenter connecting failed [6]
0	08:36:49.091	'805239': login on HTFXVULTD-Live through DC-3 (ping: 233.47 ms)
0	08:36:50.606	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 233.47 ms)
0	08:36:51.200	'805239': previous successful authorization performed from 152.32.128.46
0	08:36:58.185	'805239': auto connecting to a better access point DC-4 (ping is 230.54 ms)
0	08:36:58.982	'805239': login on HTFXVULTD-Live through DC-4 (ping: 230.54 ms)
0	08:37:00.482	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 230.54 ms)
0	08:37:01.091	'805239': previous successful authorization performed from 152.32.128.46
1	13:47:18.891	'805239': ping failed
1	13:47:18.906	'805239': datacenter connecting failed [6]
0	13:47:19.718	'805239': login on HTFXVULTD-Live through DC-3 (ping: 233.37 ms)
0	13:47:21.232	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 233.37 ms)
0	13:47:21.826	'805239': previous successful authorization performed from 152.32.128.46
0	13:47:28.897	'805239': auto connecting to a better access point DC-4 (ping is 230.51 ms)
0	13:47:29.678	'805239': login on HTFXVULTD-Live through DC-4 (ping: 230.51 ms)
0	13:47:31.223	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 230.51 ms)
0	13:47:31.848	'805239': previous successful authorization performed from 152.32.128.46
1	14:19:11.058	'805239': ping failed
1	14:19:11.058	'805239': datacenter connecting failed [6]
0	14:19:11.885	'805239': login on HTFXVULTD-Live through DC-3 (ping: 233.63 ms)
0	14:19:13.368	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 233.63 ms)
0	14:19:13.993	'805239': previous successful authorization performed from 152.32.128.46
1	14:48:35.812	'805239': datacenter connecting failed [6]
0	14:48:36.655	'805239': login on HTFXVULTD-Live through DC-1 (ping: 246.19 ms)
0	14:50:07.603	'805239': login on HTFXVULTD-Live through DC-2 (ping: 279.45 ms)
0	14:50:48.925	'805239': auto connecting to a better access point DC-4 (ping is 331.70 ms)
0	14:50:56.309	'805239': login on HTFXVULTD-Live through DC-4 (ping: 331.70 ms)
0	14:51:56.973	'805239': login datacenter on HTFXVULTD-Live
0	14:52:03.982	'805239': login on HTFXVULTD-Live through DC-3 (ping: 335.38 ms)
0	14:52:37.701	'805239': ping to current access point DC-3 is 335.41 ms
0	14:53:06.082	'805239': login datacenter on HTFXVULTD-Live
1	14:54:13.489	'805239': connect failed [一般错误]
0	14:54:27.476	'805239': ping to current access point DC-4 is n/a
0	14:54:40.621	'805239': login on HTFXVULTD-Live through DC-4 (ping: n/a)
1	14:56:02.406	'805239': datacenter connecting failed [6]
0	14:56:12.303	'805239': login on HTFXVULTD-Live through DC-3 (ping: 155.71 ms)
0	14:56:54.452	'805239': ping to current access point DC-3 is n/a
0	14:57:13.123	'805239': login datacenter on HTFXVULTD-Live
0	14:57:20.834	'805239': login on HTFXVULTD-Live through DC-4 (ping: 304.29 ms)
0	14:58:27.602	'805239': login datacenter on HTFXVULTD-Live
0	14:58:28.257	'805239': auto connecting to a better access point DC-4 (ping is 333.99 ms)
0	14:58:49.925	'805239': login on HTFXVULTD-Live through DC-4 (ping: 333.99 ms)
0	14:59:58.035	'805239': login on HTFXVULTD-Live through DC-3 (ping: 334.71 ms)
0	15:00:59.807	'805239': login datacenter on HTFXVULTD-Live
0	15:01:50.480	'805239': login on HTFXVULTD-Live through DC-1 (ping: 359.34 ms)
0	15:02:06.059	'805239': ping to current access point DC-1 is 359.89 ms
0	15:02:57.512	'805239': login on HTFXVULTD-Live through DC-4 (ping: 180.45 ms)
0	15:03:00.229	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 180.45 ms)
0	15:03:01.930	'805239': previous successful authorization performed from 152.32.128.46
0	15:03:09.720	'805239': ping to current access point DC-4 is 230.72 ms
1	15:33:50.452	'805239': datacenter connecting failed [6]
0	15:33:51.248	'805239': login on HTFXVULTD-Live through DC-3 (ping: 234.44 ms)
0	15:33:52.762	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 234.44 ms)
0	15:33:53.340	'805239': previous successful authorization performed from 152.32.128.46
1	16:09:52.548	'805239': ping failed
1	16:09:52.548	'805239': datacenter connecting failed [6]
0	16:09:53.219	'805239': login on HTFXVULTD-Live through DC-1 (ping: 243.53 ms)
0	16:09:55.280	'805239': previous successful authorization performed from 152.32.128.46
0	16:10:13.654	'805239': auto connecting to a better access point DC-4 (ping is 231.78 ms)
0	16:10:14.450	'805239': login on HTFXVULTD-Live through DC-4 (ping: 231.78 ms)
0	16:10:15.964	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 231.78 ms)
0	16:10:16.620	'805239': previous successful authorization performed from 152.32.128.46
1	17:28:15.520	'805239': ping failed
1	17:28:15.536	'805239': datacenter connecting failed [6]
0	17:28:19.360	'805239': login on HTFXVULTD-Live through DC-3 (ping: 234.21 ms)
0	17:28:20.874	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 234.21 ms)
0	17:28:21.483	'805239': previous successful authorization performed from 152.32.128.46
0	17:28:30.912	'805239': auto connecting to a better access point DC-4 (ping is 231.55 ms)
0	17:28:31.630	'805239': login on HTFXVULTD-Live through DC-4 (ping: 231.55 ms)
0	17:28:33.441	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 231.55 ms)
0	17:28:34.050	'805239': previous successful authorization performed from 152.32.128.46
1	18:05:53.232	'805239': ping failed
1	18:05:53.232	'805239': datacenter connecting failed [6]
0	18:05:54.028	'805239': login on HTFXVULTD-Live through DC-3 (ping: 234.44 ms)
0	18:05:55.574	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 234.44 ms)
0	18:05:56.167	'805239': previous successful authorization performed from 152.32.128.46
1	19:27:54.768	'805239': ping failed
1	19:27:54.783	'805239': datacenter connecting failed [6]
0	19:27:55.455	'805239': login on HTFXVULTD-Live through DC-1 (ping: 245.76 ms)
0	19:27:57.549	'805239': previous successful authorization performed from 152.32.128.46
0	19:28:04.674	'805239': auto connecting to a better access point DC-4 (ping is 230.82 ms)
0	19:28:05.471	'805239': login on HTFXVULTD-Live through DC-4 (ping: 230.82 ms)
0	19:28:06.986	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 230.82 ms)
0	19:28:07.596	'805239': previous successful authorization performed from 152.32.128.46
1	19:29:07.111	'805239': ping failed
1	19:29:07.127	'805239': datacenter connecting failed [6]
0	19:29:07.939	'805239': login on HTFXVULTD-Live through DC-3 (ping: 233.50 ms)
0	19:29:09.439	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 233.50 ms)
0	19:29:10.049	'805239': previous successful authorization performed from 152.32.128.46
1	20:35:12.596	'805239': ping failed
0	20:35:13.236	'805239': login on HTFXVULTD-Live through DC-1 (ping: 237.40 ms)
0	20:35:15.252	'805239': previous successful authorization performed from 152.32.128.46
0	20:35:22.424	'805239': auto connecting to a better access point DC-4 (ping is 230.68 ms)
0	20:35:23.252	'805239': login on HTFXVULTD-Live through DC-4 (ping: 230.68 ms)
0	20:35:24.799	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 230.68 ms)
0	20:35:25.424	'805239': previous successful authorization performed from 152.32.128.46