RTAC68U - Merlin 380.66_6 Freeze many times per day...

[Romeo-Sierra_Hotel]

Good day all,

Since I upgraded FW from 3.0.0.4.380_3264 to any (either Asus or Merlin FW) I have great
instability issues. (Router unresponsive for 2-3 minutes)... If I go back to 3.0.0.4.380_3264, the problem disappear. You'll find logs below. When it occurs, I cannot even log into the router. Sometimes it happens and no log at all. Base on the messages it looks like the router is losing connection with the modem but because I'm able to use it without any problem with old Firmware I don't think it is related to the modem. Of course, I dont want to use old FW for obvious security reasons. Any clues or advices ?

Best regards

Router : Asus RTAC68U
Current version : Merlin 380.66_6

Anything over Asus 3.0.0.4.380_3264 is unstable.

Logs :
Jul 13 19:57:39 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 13 23:30:44 WAN Connection: Ethernet link up.
Jul 13 23:30:44 rc_service: wanduck 465:notify_rc restart_wan_if 0
Jul 13 23:30:44 kernel: Attempt to kill tasklet from interrupt
Jul 13 23:30:46 rc_service: udhcpc 28046:notify_rc start_firewall
Jul 13 23:30:47 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 13 23:30:47 wan: finish adding multi routes
Jul 13 23:30:47 rc_service: udhcpc 28046:notify_rc stop_upnp
Jul 13 23:30:47 rc_service: udhcpc 28046:notify_rc start_upnp
Jul 13 23:30:47 rc_service: waitting "stop_upnp" via udhcpc ...
Jul 13 23:30:54 rc_service: udhcpc 28046:notify_rc start_firewall
Jul 13 23:30:54 dhcp client: bound XX.XXX.XXX.108 via XX.XXX.XXX.97 during 3600 seconds.
Jul 13 23:30:55 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 14 01:10:24 WAN Connection: Ethernet link up.
Jul 14 01:10:24 rc_service: wanduck 465:notify_rc restart_wan_if 0
Jul 14 01:10:24 kernel: Attempt to kill tasklet from interrupt
Jul 14 01:10:26 rc_service: udhcpc 2361:notify_rc start_firewall
Jul 14 01:10:27 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 14 01:10:27 wan: finish adding multi routes
Jul 14 01:10:28 rc_service: udhcpc 2361:notify_rc stop_upnp
Jul 14 01:10:28 rc_service: udhcpc 2361:notify_rc start_upnp
Jul 14 01:10:28 rc_service: waitting "stop_upnp" via udhcpc ...
Jul 14 01:10:34 rc_service: udhcpc 2361:notify_rc start_firewall
Jul 14 01:10:34 dhcp client: bound XX.XXX.XXX.108 via XX.XXX.XXX.97 during 3600 seconds.
Jul 14 01:10:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!

 

[skeal]

I have same router and same firmware. I never see this line in my logs.

Jul 13 23:30:44 rc_service: wanduck 465:notify_rc restart_wan_if 0

You may want to start there. The kernel seems to have a problem with this tasklet.

 

[skeal]

I have same router and same firmware. I never see this line in my logs.

Jul 13 23:30:44 rc_service: wanduck 465:notify_rc restart_wan_if 0

You may want to start there. The kernel seems to have a problem with this tasklet.

Try running this from command prompt.

nvram set web_redirect=0

Regards

 

[john9527]

It's this line which is of concern....
Jul 13 23:30:44 WAN Connection: Ethernet link up.

This means the router-modem connection failed. You should look for a corresponding 'link down' message earlier. If there isn't a 'link down' message it means the interface is having quickly recovered dropouts.

First thing to try is to replace the modem to router cable with a good quality cat5e or cat6 cable.

As to the apparent fw level sensitivities, there may have been an ethernet driver change that is stressing the connection more.

 

[skeal]

It's this line which is of concern....
Jul 13 23:30:44 WAN Connection: Ethernet link up.

This means the router-modem connection failed. You should look for a corresponding 'link down' message earlier. If there isn't a 'link down' message it means the interface is having quickly recovered dropouts.

First thing to try is to replace the modem to router cable with a good quality cat5e or cat6 cable.

As to the apparent fw level sensitivities, there may have been an ethernet driver change that is stressing the connection more.

Thanks John!

 

[Romeo-Sierra_Hotel]

Hello Skeal and John. I moved my router closer to the modem. I also changed the cable for a new one.

Thanks for your inputs.

I'll get back to post the results after a few days.

Regards

 

[Romeo-Sierra_Hotel]

Just as information,

The cause of my problems were related to defective, unreliable modem. I had a hard time to get support from my ISP who taught that it was related to the router, despite their logs showing multiple disconnects per day, modem replaced and not a single disconnect since.

Regards,

Patrice.