Computer locks - takes down internet for entire house (until I reboot system)

thepregnantgod

Distinguished
Jan 12, 2010
261
0
18,780
Folks, I'm having some weird stuff happening. My main rig 6900k, Win10x64 hooked to an AP, hooked to my main Asus RT-AC5300 router locks. I suspect it's because of instability - though it only happens when I'm not around. I've stressed tested with for 10hrs plus and no faults.

But inevitably, I'll find it locked and my family says internet is down. I go home, power off/on system and without touching the router at all - the WAN immediately becomes available.

I suspected something fishy with the router so I downloaded the official firmware, updated, changed my password to a 20 character password, secured everything (no UPNP, etc.) and it's still happening. See the log below if you can translate it would be much appreciated.

Oct 19 23:00:12 disk_monitor: Got SIGALRM...
Oct 19 23:11:09 WAN Connection: DNS probe failed (0/2)
Oct 19 23:11:16 WAN Connection: DNS probe failed (1/2)
Oct 19 23:11:23 WAN Connection: DNS probe failed (2/2)
Oct 19 23:16:57 WAN Connection: ISP's DHCP did not function properly.
Oct 19 23:16:57 DualWAN: skip single wan wan_led_control - WANRED off
Oct 19 23:16:57 stop_nat_rules: apply the redirect_rules!
Oct 20 05:03:29 rc_service: udhcpc 31303:notify_rc start_firewall
Oct 20 05:03:29 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Oct 20 05:03:29 wan: finish adding multi routes
Oct 20 05:03:29 rc_service: udhcpc 31303:notify_rc stop_upnp
Oct 20 05:03:29 rc_service: waitting "start_firewall" via udhcpc ...
Oct 20 05:03:30 rc_service: udhcpc 31303:notify_rc start_upnp
Oct 20 05:03:30 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 20 05:03:32 WAN Connection: DNS probe succeeded (50/2)
Oct 20 05:03:32 WAN Connection: WAN was restored.
Oct 20 05:03:35 rc_service: udhcpc 31303:notify_rc start_firewall
Oct 20 05:03:35 dhcp client: bound 76.208.80.91 via 76.208.80.1 during 600 seconds.
Oct 20 05:03:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Oct 20 09:08:54 WAN Connection: DNS probe failed (0/2)
Oct 20 09:09:01 WAN Connection: DNS probe failed (1/2)
Oct 20 09:09:08 WAN Connection: DNS probe failed (2/2)
Oct 20 09:18:33 WAN Connection: ISP's DHCP did not function properly.
Oct 20 09:18:33 DualWAN: skip single wan wan_led_control - WANRED off
Oct 20 09:18:33 stop_nat_rules: apply the redirect_rules!
Oct 20 10:06:38 rc_service: udhcpc 20502:notify_rc start_firewall
Oct 20 10:06:39 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Oct 20 10:06:39 wan: finish adding multi routes
Oct 20 10:06:39 rc_service: udhcpc 20502:notify_rc stop_upnp
Oct 20 10:06:39 rc_service: waitting "start_firewall" via udhcpc ...
Oct 20 10:06:40 rc_service: udhcpc 20502:notify_rc start_upnp
Oct 20 10:06:40 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 20 10:06:41 WAN Connection: DNS probe succeeded (83/2)
Oct 20 10:06:41 WAN Connection: WAN was restored.
Oct 20 10:06:44 rc_service: udhcpc 20502:notify_rc start_firewall
Oct 20 10:06:44 dhcp client: bound 76.208.80.91 via 76.208.80.1 during 600 seconds.
Oct 20 10:06:45 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
 
Solution
Do you know which version of the firmware you had before you updated? I searched for a bit, and other people using that router have been experiencing the same problem after updating to 3.0.0.4.380.3941.

http://www.snbforums.com/threads/asus-rt-5300-version-3-0-0-4-380-3941.34015/

Most of them have given up and reverted to version 3.0.0.4.380.3341.
Do you know which version of the firmware you had before you updated? I searched for a bit, and other people using that router have been experiencing the same problem after updating to 3.0.0.4.380.3941.

http://www.snbforums.com/threads/asus-rt-5300-version-3-0-0-4-380-3941.34015/

Most of them have given up and reverted to version 3.0.0.4.380.3341.
 
Solution