A forum to discuss the Gargoyle web interface for Openwrt
https://www.gargoyle-router.com/phpbb/
Do a failsafe reset.dg_102 wrote:Hi,
I did upgrade 1.9.1 to this version on TL-WDR4300 v1, unfortunately now it reboots on it's own about 5-10 seconds after it comes up.
Any ideas what can I do?
Thank you,
dg.
Hi did you save settings? If so you will have to do a falesafe.dg_102 wrote:Hi,
I did upgrade 1.9.1 to this version on TL-WDR4300 v1, unfortunately now it reboots on it's own about 5-10 seconds after it comes up.
Any ideas what can I do?
Thank you,
dg.
Code: Select all
Reply[1] from 192.168.1.2: bytes=10240 time=6.6 ms TTL=64
Reply[2] from 192.168.1.2: bytes=10240 time=4.8 ms TTL=64
Reply[3] from 192.168.1.2: bytes=10240 time=9.3 ms TTL=64
Reply[4] from 192.168.1.2: bytes=10240 time=131.0 ms TTL=64
Reply[5] from 192.168.1.2: bytes=10240 time=43.5 ms TTL=64
Reply[6] from 192.168.1.2: bytes=10240 time=113.6 ms TTL=64
Reply[7] from 192.168.1.2: bytes=10240 time=11.4 ms TTL=64
Reply[8] from 192.168.1.2: bytes=10240 time=5.9 ms TTL=64
Reply[9] from 192.168.1.2: bytes=10240 time=9.5 ms TTL=64
Reply[10] from 192.168.1.2: bytes=10240 time=9.9 ms TTL=64
Reply[11] from 192.168.1.2: bytes=10240 time=4.9 ms TTL=64
Reply[12] from 192.168.1.2: bytes=10240 time=10.5 ms TTL=64
Reply[13] from 192.168.1.2: bytes=10240 time=6.7 ms TTL=64
Reply[14] from 192.168.1.2: bytes=10240 time=6.3 ms TTL=64
Reply[15] from 192.168.1.2: bytes=10240 time=11.9 ms TTL=64
Reply[16] from 192.168.1.2: bytes=10240 time=46.5 ms TTL=64
Reply[17] from 192.168.1.2: bytes=10240 time=7.3 ms TTL=64
Reply[18] from 192.168.1.2: bytes=10240 time=63.1 ms TTL=64
Reply[19] from 192.168.1.2: bytes=10240 time=206.1 ms TTL=64
Reply[20] from 192.168.1.2: bytes=10240 time=29.5 ms TTL=64
Reply[21] from 192.168.1.2: bytes=10240 time=37.1 ms TTL=64
Reply[22] from 192.168.1.2: bytes=10240 time=9.5 ms TTL=64
Reply[23] from 192.168.1.2: bytes=10240 time=8.2 ms TTL=64
It seems to me that this, as always only 941nd v3. Unsuccessful modelLantis wrote:Lots didn't reveal anything unusual.
I'm not seeing this error on my end. Works fine at 40mhz
I wondered that.dg_102 wrote:Failsafe reset worked like a charm. And yes, I did preserve settings. It was from 1.9.1 to 1.9.x
Thank you Tapper and Lantis.
dg
What if you put a "big friendly reminder" as stated in this post ?ispyisail wrote: I wondered that.
Even with a big warning sign not to preserve settings?
