Hello All,
After one month internal test for running NKN Full Node on 2 Chinese brand home wifi routers(Youku YK-L1 & Lenovo NEWIFI3), now I‘m pleased to announce that Narwhal Full Node has been successfuly ported to below 4 ASUS wifi router. Hope everyone enjoy NKN mainnet mining.
RT-N56U
RT-N56UB1
RT-N65U
RT-AC1200HP
RT-N56U
RT-N56UB1
RT-N65U
RT-AC1200HP
More firmware to be added.
手动点赞:100:
This is awesome nice work!
I have one of those Asus wifi router lying around in the house, and will give it a try when Allen you release the firmware.
which model you have? I just released 2 models, and 2 more will be released soon.
My old router is RT-AC56U, maybe it is a bit too old…
This router can run nkn perfectly, but not with my firmware.
OpenWRT?
Hey.
Finally I got my ASUS RT-N56U for $ 20, although it was already used.
I have successfully configured the node by downloading the firmware from this forum. The network node worked correctly for 1 day.
Now I have a problem.
Node offline.
The system log of the router gives information (these are the last lines):
Jul 18 00:09:58 nknd: Start NKN node
Jul 18 00:10:28 watchdog: nknd is missing, start again!
Jul 18 00:10:28 nknd: Stop NKN node
Jul 18 00:10:28 nknd: Restart by watchdog(153)
Jul 18 00:10:28 nknd: Start NKN node
Jul 18 00:10:58 watchdog: nknd is missing, start again!
Jul 18 00:10:58 nknd: Stop NKN node
Jul 18 00:10:58 nknd: Restart by watchdog(154)
Jul 18 00:10:58 nknd: Start NKN node
I understand that the node cannot start and does this cyclically.
At the same time the Internet works.
The node log writes this:
2019/07/17 19:51:41.476048 [INFO ] GID 96, Load remote node 7a6b32c898ae9068eacc744c480ecdef007eaadac9f33b7668e0e0d5610f0863@tcp://209.97.180.136:30001<209.97.180.136:30001> from list
2019/07/17 19:51:41.495598 [INFO ] GID 96, Load remote node <183.136.117.109:30001> from list
2019/07/17 19:51:41.497128 [INFO ] GID 96, Load remote node 7a6d39f9885337af4f2ac1561131fe305effbd55fd837260cd57df775d5dfe9e@tcp://194.1.237.138:30001<194.1.237.138:30001> from list
2019/07/17 19:51:41.501445 [INFO ] GID 96, Load remote node 7a6ed217f5bc0943f2ed6c0d872edf15ffe3770222427b1cbcd4c299f37b2aa9@tcp://149.28.227.58:30001<149.28.227.58:30001> from list
2019/07/17 19:51:41.518051 [INFO ] GID 96, Load remote node <172.105.35.110:30001> from list
2019/07/17 19:51:41.519053 [INFO ] GID 96, Load remote node 7a712a33e13716a4720dae93a06b3115f25b23cb2785d51e3e5bc7931a568cb2@tcp://51.83.125.82:30001<51.83.125.82:30001> from list
2019/07/17 19:51:41.548793 [INFO ] GID 82, Remote node connect from 3.94.146.193:42292 to local address 95.106.152.167:30001
2019/07/17 19:51:41.575839 [INFO ] GID 257, Set min verifiable height to 63009
2019/07/17 19:51:43.426322 [INFO ] GID 82, Remote node connect from 114.217.175.248:29481 to local address 95.106.152.167:30001
2019/07/17 19:51:45.062921 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.069079 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.099228 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.212088 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.221567 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.231873 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.284664 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:45.535212 [INFO ] GID 82, Remote node connect from 167.71.179.91:39242 to local address 95.106.152.167:30001
2019/07/17 19:51:45.605009 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:46.277543 [INFO ] GID 82, Remote node connect from 35.244.123.196:57180 to local address 95.106.152.167:30001
2019/07/17 19:51:46.478975 [INFO ] GID 82, Remote node connect from 172.104.17.187:40276 to local address 95.106.152.167:30001
2019/07/17 19:51:47.455354 [INFO ] GID 82, Remote node connect from 192.227.142.101:43460 to local address 95.106.152.167:30001
2019/07/17 19:51:48.540463 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:49.541171 [INFO ] GID 82, Remote node connect from 104.248.210.216:41734 to local address 95.106.152.167:30001
2019/07/17 19:51:49.659669 [INFO ] GID 82, Remote node connect from 121.227.163.250:46478 to local address 95.106.152.167:30001
2019/07/17 19:51:50.083674 [INFO ] GID 82, Remote node connect from 134.209.63.247:42204 to local address 95.106.152.167:30001
2019/07/17 19:51:50.530203 [INFO ] GID 82, Remote node connect from 35.222.93.162:50352 to local address 95.106.152.167:30001
2019/07/17 19:51:50.875240 [INFO ] GID 82, Remote node connect from 68.183.174.76:47024 to local address 95.106.152.167:30001
2019/07/17 19:51:51.054681 [INFO ] GID 82, Remote node connect from 157.230.127.241:39502 to local address 95.106.152.167:30001
2019/07/17 19:51:51.088629 [INFO ] GID 82, Remote node connect from 34.207.146.222:38836 to local address 95.106.152.167:30001
2019/07/17 19:51:51.582837 [WARN ] GID 254, Handle proposal error: Wait for proposal timeout
2019/07/17 19:51:52.153832 [INFO ] GID 82, Remote node connect from 117.28.73.5:13680 to local address 95.106.152.167:30001
2019/07/17 19:51:52.614324 [INFO ] GID 82, Remote node connect from 178.128.6.170:59826 to local address 95.106.152.167:30001
2019/07/17 19:51:52.810965 [INFO ] GID 82, Remote node connect from 46.101.2.119:60108 to local address 95.106.152.167:30001
2019/07/17 19:51:53.654641 [INFO ] GID 82, Remote node connect from 121.236.126.164:9689 to local address 95.106.152.167:30001
2019/07/17 19:51:54.378050 [INFO ] GID 82, Remote node connect from 192.3.124.86:55194 to local address 95.106.152.167:30001
2019/07/17 19:51:54.875979 [INFO ] GID 82, Remote node connect from 134.209.12.195:47748 to local address 95.106.152.167:30001
2019/07/17 19:51:54.911088 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63561 instead of 63005
2019/07/17 19:51:56.000525 [INFO ] GID 82, Remote node connect from 60.189.208.148:48660 to local address 95.106.152.167:30001
2019/07/17 19:51:57.377110 [INFO ] GID 82, Remote node connect from 167.71.95.100:50468 to local address 95.106.152.167:30001
2019/07/17 19:51:59.969286 [INFO ] GID 82, Remote node connect from 139.59.184.14:41924 to local address 95.106.152.167:30001
2019/07/17 19:52:01.190729 [INFO ] GID 82, Remote node connect from 54.90.187.27:43186 to local address 95.106.152.167:30001
2019/07/17 19:52:01.682351 [WARN ] GID 254, Handle proposal error: Wait for neighbor vote timeout
2019/07/17 19:52:02.565336 [INFO ] GID 82, Remote node connect from 167.71.184.211:54320 to local address 95.106.152.167:30001
2019/07/17 19:52:03.062000 [INFO ] GID 82, Remote node connect from 222.78.194.4:48320 to local address 95.106.152.167:30001
2019/07/17 19:52:04.268306 [INFO ] GID 82, Remote node connect from 45.79.162.155:57312 to local address 95.106.152.167:30001
2019/07/17 19:52:04.568840 [INFO ] GID 82, Remote node connect from 183.153.147.138:41082 to local address 95.106.152.167:30001
2019/07/17 19:52:04.619354 [INFO ] GID 82, Remote node connect from 107.172.83.117:60454 to local address 95.106.152.167:30001
2019/07/17 19:52:04.651044 [INFO ] GID 82, Remote node connect from 198.46.223.114:35668 to local address 95.106.152.167:30001
2019/07/17 19:52:06.566725 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.569084 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.580215 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.583159 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.596766 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.668560 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.754995 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.767300 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.781036 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.783769 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.787175 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.791696 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.794856 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.801972 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.803739 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.828706 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.849506 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.903277 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.920852 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.938783 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.940640 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.976226 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.986577 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.989845 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:06.994112 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:07.149226 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:07.252651 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:07.371371 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:07.430540 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:07.496570 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:08.067135 [INFO ] GID 82, Remote node connect from 183.148.174.80:52978 to local address 95.106.152.167:30001
2019/07/17 19:52:08.137520 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:08.335647 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:08.637184 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:09.040953 [INFO ] GID 82, Remote node connect from 34.229.90.75:50374 to local address 95.106.152.167:30001
2019/07/17 19:52:10.580389 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:10.584678 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:10.652129 [INFO ] GID 82, Remote node connect from 115.216.194.229:52188 to local address 95.106.152.167:30001
2019/07/17 19:52:11.771780 [WARN ] GID 254, Handle proposal error: Wait for neighbor vote timeout
2019/07/17 19:52:12.288360 [INFO ] GID 82, Remote node connect from 51.158.183.156:50356 to local address 95.106.152.167:30001
2019/07/17 19:52:12.628056 [INFO ] GID 257, Set min verifiable height to 63568
2019/07/17 19:52:13.006954 [INFO ] GID 82, Remote node connect from 107.182.22.103:53492 to local address 95.106.152.167:30001
2019/07/17 19:52:13.104098 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:13.645073 [INFO ] GID 82, Remote node connect from 49.72.70.43:40431 to local address 95.106.152.167:30001
2019/07/17 19:52:14.093444 [INFO ] GID 82, Remote node connect from 178.128.195.194:46154 to local address 95.106.152.167:30001
2019/07/17 19:52:17.694294 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63005
2019/07/17 19:52:21.700726 [WARN ] GID 279, Ping 7a6802d6d84f111e2a2560e7e7f36e27f8f25191ed96b126f554fa59a9565359@tcp://114.217.175.248:30001<114.217.175.248:29481> error: Wait for reply timeout
2019/07/17 19:52:21.843224 [WARN ] GID 254, Handle proposal error: Wait for neighbor vote timeout
2019/07/17 19:52:21.858480 [ERROR] GID 1220, Error sending sync messge to node: Wait for reply timeout
2019/07/17 19:52:21.859019 [WARN ] GID 1220, Get consensus state from neighbor 7a6802d6d84f111e2a2560e7e7f36e27f8f25191ed96b126f554fa59a9565359 error: Wait for reply timeout
2019/07/17 19:52:21.859662 [INFO ] GID 257, Set min verifiable height to 63569
2019/07/17 19:52:21.894095 [INFO ] GID 254, Change expected block height to 63564
2019/07/17 19:52:24.182210 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63564
2019/07/17 19:52:24.868714 [WARN ] GID 113, Ping 7a6c4df97428d1c6b8626cefa1f1b66a2ea6bbc8b86e87b4842c1df41d933378@tcp://183.136.117.109:30001<183.136.117.109:30001> error: Wait for reply timeout
2019/07/17 19:52:26.476143 [INFO ] GID 82, Remote node connect from 107.173.213.43:54703 to local address 95.106.152.167:30001
2019/07/17 19:52:28.021126 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63562 instead of 63564
2019/07/17 19:52:28.252757 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.255407 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.260769 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.274434 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.283551 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.285063 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.293843 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.336480 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.343582 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.390020 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.392686 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.396607 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.418993 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.427922 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.442903 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.447452 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.456242 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.459247 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.474674 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.477018 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.479300 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.481269 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.492112 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.495143 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.506296 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.528440 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.531184 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.566096 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.603960 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.612962 [WARN ] GID 685, Ping 7a55013f598c9ce0cfd3a07dc74c7b2818dff01fd7d41af53d48d6f7f77ac7ed@tcp://121.236.126.164:30001<121.236.126.164:9689> error: Wait for reply timeout
2019/07/17 19:52:28.821350 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.860308 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:28.988323 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:29.095484 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:29.163683 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:29.259581 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:29.369533 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:29.911676 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:30.807575 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:31.018435 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:31.720939 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:31.912782 [WARN ] GID 254, Handle proposal error: Wait for neighbor vote timeout
2019/07/17 19:52:32.560656 [ERROR] GID 1283, Error sending sync messge to node: Wait for reply timeout
2019/07/17 19:52:32.561183 [WARN ] GID 1283, Get consensus state from neighbor 7a55013f598c9ce0cfd3a07dc74c7b2818dff01fd7d41af53d48d6f7f77ac7ed error: Wait for reply timeout
2019/07/17 19:52:32.565430 [ERROR] GID 1286, Error sending sync messge to node: Wait for reply timeout
2019/07/17 19:52:32.566147 [WARN ] GID 1286, Get consensus state from neighbor 7a6c4df97428d1c6b8626cefa1f1b66a2ea6bbc8b86e87b4842c1df41d933378 error: Wait for reply timeout
2019/07/17 19:52:36.944445 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:39.896512 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:41.907986 [INFO ] GID 82, Remote node connect from 54.198.18.175:56738 to local address 95.106.152.167:30001
2019/07/17 19:52:41.996851 [WARN ] GID 254, Handle proposal error: Wait for neighbor vote timeout
2019/07/17 19:52:42.133725 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:42.975320 [INFO ] GID 82, Remote node connect from 117.81.183.102:51261 to local address 95.106.152.167:30001
2019/07/17 19:52:44.311710 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:47.999771 [WARN ] GID 79, Error handling msg: Receive invalid block hash height 63563 instead of 63564
2019/07/17 19:52:49.742024 [INFO ] GID 256, Request block d696fb06688cad0f568a7930412ab10ccb88a240b77071a843469aa16364a809 from neighbor 7a69dde4324bf184b6a3279c59603a90ee4a84df1fb9c40459069646cae75c46
2019/07/17 19:52:49.876504 [INFO ] GID 256, Receive block info d696fb06688cad0f568a7930412ab10ccb88a240b77071a843469aa16364a809, 0 txn found in pool, 2 txn to request
2019/07/17 19:52:50.022707 [INFO ] GID 256, Receive block proposal d696fb06688cad0f568a7930412ab10ccb88a240b77071a843469aa16364a809 (2 txn, 3236 bytes) by 0145ade3af85427a9931583e551b32fa764b1a1edf58096e803c17f659faacb6
2019/07/17 19:52:56.585432 [INFO ] GID 82, Remote node connect from 3.88.235.36:60294 to local address 95.106.152.167:30001
2019/07/17 19:52:56.826270 [INFO ] GID 82, Remote node connect from 107.172.157.209:56330 to local address 95.106.152.167:30001
2019/07/17 19:52:57.308842 [INFO ] GID 82, Remote node connect from 52.91.170.189:47646 to local address 95.106.152.167:30001
2019/07/17 19:52:57.943010 [ERROR] GID 1479, Error sending sync messge to node: Wait for reply timeout
2019/07/17 19:52:57.943554 [WARN ] GID 1479, Get consensus state from neighbor 766207d4ece3349bd225dc772eba31494bf57571720454bbe8cff6521420eee2 error: Wait for reply timeout
2019/07/17 19:52:59.763602 [INFO ] GID 254, Change expected block height to 63565
2019/07/17 19:53:02.138128 [WARN ] GID 1163, Ping 766207d4ece3349bd225dc772eba31494bf57571720454bbe8cff6521420eee2@tcp://49.72.70.43:30001<49.72.70.43:40431> error: Wait for reply timeout
2019/07/17 19:53:02.464866 [INFO ] GID 82, Remote node connect from 45.77.230.189:56346 to local address 95.106.152.167:30001
2019/07/17 19:53:04.596808 [INFO ] GID 82, Remote node connect from 3.121.116.222:35932 to local address 95.106.152.167:30001
I understand that the node does not see the network.
What can be problematic?
UPD
After restarting the router, the NKN node does not start.
I cannot turn it on by specifying the wallet.json and password.
After clicking on the apply button, nothing happens.
UPD
I found that after rebooting the router does not see see usb disk. After reconnecting the usb disk, the router began to see it. But the log of the router reported that the NKN node was stopped, because the usbdisk is unavailable. I connected the other disk. Perhaps the reason was this.
Sync started.
We will observe.
Hi Allen.
the unstable usb disk maybe your root cause, aleksey.
if your router could keep running nkn with your new usb disk, then everything would be fine.
BTW, $20 for an asus wifi router is a very acceptable price, right?
I also had the problem of disconnecting the Internet, where I had to re-compress the cable connector.
I watched the work of the node in recent days, it works stably. But also stable I have no reward. 
This is a good price for a router. But this is a big price for the node, the payback period of which tends to infinity.:бесконечность:
Can you get a working full node for asus gt-ax11000?