My RUTX12 was not functioning correctly, so I decided to reset into bootloader mode. My laptop is in the correct network and I can ping the 192.168.1.1 address very briefly (perhaps 10 packets) before it becomes unreachable again. A web-browser loading that page loads the firmware message, and then becomes un-responsive. Is the unit bricked?
Request timeout for imp_seq 668
Request timeout for imp_seq 669
64 bytes from 192.168.1.1: icmp_seq=670 ttl=64 time=78.908 ms
64 bytes from 192.168.1.1: icmp_seq=671 ttl=64 time=65.974 ms
64 bytes from 192.168.1.1: icmp_seq=672 ttl=64 time=49.880 ms
64 bytes from 192.168.1.1: icmp_seq=673 ttl=64 time=34.116 ms
64 bytes from 192.168.1.1: icmp_seq=674 ttl=64 time=17.661 ms
64 bytes from 192.168.1.1: icmp_seq=675 ttl=64 time=49.366 ms
64 bytes from 192.168.1.1: icmp_seq=676 ttl=64 time=73.041 ms
Request timeout for icmp_seq 677
Request timeout for icmp_seq 678
Please… Just to be sure…
Your PC, don’t have another network interface (WiFi or cable), because… the ping time is very high for a PC connected direct to device in bootloader mode.
Should be something, like this.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=62 time=1.39 ms
Yes, it was the only network interface enabled at the time. In the end I tried the bootloader about 10 times, and then went back to a factory reset, and I left it pinging in the background. After an hour or so, it started pinging, so I opened 192.168.1.1, and I could log in. Not sure what happened, but I upgraded the firmware in the device, and it seems to be functioning OK now. Thanks for your reply.