Gargoyle Forum

Here's what I did: - upgrade to new build, do not preserve settings - configured Eastern Time Zone, continued to configure as normal (wireless settings, IP, DHCP, restrictions, etc) - used it as normal (streamed a movie, browsed websites, etc) - noticed that a restriction came into place incorrectly...

when the system boots up, the time gets shifted after (i think) the data gets reloaded and causes a panic. system then reboots again. The process continues indefinitely. Is this a reported bug that will be fixed? To me, this is a system stability issue that could cause people to abandon Gargoyle co...

Can you explain why the time would cause reboots, when it was ok before the reboot?

Maybe it has something to do with Daylight Saving Time? I'm going to wait until after the changeover as a precaution, because there were issues with it in the past. Lantis was right - it needed a reboot to readjust the base time. Unfortunately, I used the "reboot" command from the menu in...

Lantis wrote: Either reboot router or issue
/etc/init.d/system restart

To update the time.

Thanks! I guess I haven't done that since upgrading. I'll give it a shot.

I'm going to test some more, but I think there is a time bug in this build. Even though I have set the time zone, it appears that all time is being evaluated based on UTC. The current time shows UTC The restrictions seem to trigger off of UTC time and not my local time zone Any idea why this would h...

Confirmed bootloop issue on this build. I saved a revised firewall restriction, after it running for days, and it started the reboot loop. Disconnecting the Ethernet/internet cable stopped the rebooting and allowed me to log in. Clearing the bandwidth usage seems to have fixed it, as all appears to ...

+1 for sure

I would like my kids to have a filtered DNS whereas me and my wife have non-filtered.

I'd prefer something stable rather than waiting for bug fixes all the time. Something absolutely brand new like cc? Maybe after a while

Try disconnecting the router from everything else, and see if it still gives any DHCP addresses. I have encountered something similar to this, and just now trying to understand it. It looks like it is passing the DHCP request instead of serving the IP, under certain circumstances