Question

Hello, I have new RUTX11 (one week old) (RUTX_R_00.07.02.1) and when I connect via Wi-Fi the router suddenly reboots after a period. When there are no Wi-Fi connections the RUTX11 is stable, it has been running perfectly last weekend until I started connecting to Wi-Fi yesterday. The strange thing is that I used a Lenovo laptop last week where I did not have problems and yesterday a HP laptop where I did notice the reboots. I checked the log files but there is nothing because it does not retain the logs before the reboot. The power cable is also ok because nothing happens when I tap on it. Any ideas, could the unit drain to much power?

Answer 1

Hello,

Does the router reboot with any device trying to connect to it via WiFI?

Does it show any unusual behavior, for example, heating, blinking leds, slow response? 

To try and register anything from the router side, access the router via CLI/SSH, then enter the following command: logread -f. Next, connect to the router with the WiFi and check, if anything spawns in the logs before the restart.

Best regards,

Žygimantas

Comments

Hello Žygimantas,

Heating is fine, leds are following standard boot procedure and no slow response.

I will try the logread function, I also setup a remote syslog server to catch errors.

Thanks for your response.

Best regards,

Jan

---

Hello Žygimantas,

I have run the commands with a CLI connection but the last message is that a client connects and then the reboots happen without any additional information from the CLI. I attached a text file with the comments and a video file of the reboot (2 times). I also have a movie of the reboot, please let me know how to sent is.

What i also tried is: disabling Bluetooth and GPS, nog change.
I also tries enabling only 2.4, or only the 5GHz but the router still reboots.
Also different clients where used, two laptops, phones.

In the main message i attached the CLI.log and a troubleshoot file.
 

---

In order to get kernel backtraces in case of oom oops or panic you need to redirect the logs to a remote syslogd, logread will not be scheduled anymore and won't show anything. I have been able to capture backtraces this way.

Setting /proc/sys/kernel/panic_on_oops to 0 may help you, the router won't immediately reboot.

---

Hello flebourse,

I changed the panic_on_oops to zero but the router did reboot again.
Also the last line of the remote syslog are, there is nothing usefull in there (I also attached a log file to the original post):

30>Jun 27 14:10:36 router_training hostapd: wlan0: STA 02:fe:92:74:b6:6b WPA: pairwise key handshake completed (RSN) 172.30.100.1 27/06 14:10:36.403

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPDISCOVER(br-lan) 02:fe:92:74:b6:6b 172.30.100.1 27/06 14:10:39.635

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPOFFER(br-lan) 172.30.100.153 02:fe:92:74:b6:6b 172.30.100.1 27/06 14:10:39.637

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPDISCOVER(br-lan) 02:fe:92:74:b6:6b 172.30.100.1 27/06 14:10:39.638

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPOFFER(br-lan) 172.30.100.153 02:fe:92:74:b6:6b 172.30.100.1 27/06 14:10:39.640

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPREQUEST(br-lan) 172.30.100.153 02:fe:92:74:b6:6b 172.30.100.1 27/06 14:10:39.698

<30>Jun 27 14:10:39 router_training dnsmasq-dhcp[5447]: DHCPACK(br-lan) 172.30.100.153 02:fe:92:74:b6:6b S22-van-Jan 172.30.100.1 27/06 14:10:39.700

<6>Jun 27 14:10:39 router_training Leased 172.30.100.153 IP address for client 02:fe:92:74:b6:6b - S22-van-Jan in WiFi 172.30.100.1 27/06 14:10:39.780

REBOOT

Best regards,

Jan

---

Hello,

I suggest to contact you distributor for replacement or warranty repair.

Best regards,

Žygimantas