Rebooting every 1-2 minutes
Posted: Sat Apr 01, 2017 1:04 am
I have a TP-Link Archer-C7 AC1750 running Gargoyle v1.9.1 since mid January. Outside of some issues in first week dropping WAN it's been running fine.
Today I tweaked the QoS Up/Down max rates and re-enabled a user quota. After applying settings the router began behaving strangely, dropping connections frequently. Watching the lights on the router it looks like it's rebooting about every 1 to 2 minutes.
From a wired Windows workstation I set a continuous ping to the router. There is a reply with <1ms delay for about 1minute, then 3 or 4 timeouts in a row, then "destination host unreachable", then a couple more timeouts, then a handful of reply, a few more timeouts, and then 1 or 2 minutes of continuous reply. And then repeat.
Powering off the router for 1 minute does not change the pattern. Neither does rebooting from the web Admin panel.
Within the 1 or 2 minute time "it's on" time interval I've been able to login long enough to disable QoS and all but one active quota (there were 6), and issue controlled reboot. No change observed.
I also upgraded the firmware to v1.9.2, preserving settings. no change. (thanks for mobile interface!)
The ping behaviour and reboot cycle has not varied for at least the last 1.5 hrs.
[update] I tried to attach the ping log but the forum tells me .txt and .log are invalid extensions.
Today I tweaked the QoS Up/Down max rates and re-enabled a user quota. After applying settings the router began behaving strangely, dropping connections frequently. Watching the lights on the router it looks like it's rebooting about every 1 to 2 minutes.
From a wired Windows workstation I set a continuous ping to the router. There is a reply with <1ms delay for about 1minute, then 3 or 4 timeouts in a row, then "destination host unreachable", then a couple more timeouts, then a handful of reply, a few more timeouts, and then 1 or 2 minutes of continuous reply. And then repeat.
Code: Select all
{...}
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
{...}Within the 1 or 2 minute time "it's on" time interval I've been able to login long enough to disable QoS and all but one active quota (there were 6), and issue controlled reboot. No change observed.
I also upgraded the firmware to v1.9.2, preserving settings. no change. (thanks for mobile interface!)
The ping behaviour and reboot cycle has not varied for at least the last 1.5 hrs.
[update] I tried to attach the ping log but the forum tells me .txt and .log are invalid extensions.
...but now we've lost our usage stats, which is the reason we're using Gargoyle and not factory firmware. 
