Gargoyle Forum

Status Update:
As per IspyIsail suggestion to do a failsafe reset and retest, I attempted to perform a "Restore Default Configuration".
I was not successful, so I decided to re-install the same firmware "Gargoyle Version:1.7.X (Built 20150604-0528 git@e7e4e5e)" over the already installed one but without the attempt to preserve settings.

After successful re-installation, I configured only minimal settings, specific to my network.
Results after 24 hours: No reboots... Yahoo
It is possible that preserving settings from a previous firmware revision of 1.7.0 to 1.7.1 had something to do with the reboots.
Similarly, when I upgraded and preserved the settings from 1.7.1 to 1.7.X (currently installed)

Now I will proceed to slowly add more configuration settings and monitor the progress.

Updates to follow in the next 24 hours...

Update.
Well, after another 24 hours no reboots with additional settings added.
I will add more custom settings and continue to monitor.
next update will be approximately 24 hours from now.

Thanks

keep us updated

Early status update:
Today the router rebooted over 5 times according to my kids as the experienced internet disruptions after school. I also experienced this when I connected to the network when I got home.
The only changes that were made were the adding of some "Static IP Address" And adding a Quota entry:
I will be removing the Quotas and continue to monitor the situation.

Status update:
Well, I definitely found the setting that causes my router to reboot when performing a speedtest.

After 24 hours of no reboots, I added one setting and that is the Quotas. It is after I added this entry that the router will reboot during a speedtest.
I can reproduce this issue very easily by going to this speedtest site:
http://www.dslreports.com/speedtest
and performing a test with CABLE as the connection type as this is what I have. at the time of this post, I have been able to reproduce the reouter reboots, at least 1 reboot for every 2 speedtests.

I really hope that you can reproduce this issue so that the problem can be identified and fixed.
Otherwise I will be forced to downgrade my D-Link DIR-835 Rev. A1 to v1.6.2 as this issue is not in that release.

As I was writing this update, the router rebooted and there were 2 others on the network both were using "Google Docs" editing their homework.

Thanks

I have a suggestion, and no idea if it will fix it or not but it may be worth a try (maybe after the kids finish their homework )

Can you setup enable QoS both upload and download.
In each make One class called Throttle

Make the throttle class 1%
In the throttle class make the maximum bandwidth setting what you are trying to do in the quotas section (be mindful that here it is Kbps not KB/s).
Set the default class to normal.

Now on your quotas page, under throttling it should let you set it to a class instead of a speed.

See if that produces the crashes also. That is the only difference between my setup and yours and I wasn't able to reproduce your crash. In essence this achieves the same outcome as what you are doing, just a different way.

Just an FYI... (You guys are "Awesome" I truly think that this is the best router firmware available without breaking the bank to buy one.)

Here are 2 successful speedtest results:
http://www.speedtest.net/ http://www.dslreports.com/speedtest

Lantis wrote:I have a suggestion, and no idea if it will fix it or not but it may be worth a try (maybe after the kids finish their homework )

Can you setup enable QoS both upload and download.
In each make One class called Throttle

Make the throttle class 1%
In the throttle class make the maximum bandwidth setting what you are trying to do in the quotas section (be mindful that here it is Kbps not KB/s).
Set the default class to normal.

Now on your quotas page, under throttling it should let you set it to a class instead of a speed.

See if that produces the crashes also. That is the only difference between my setup and yours and I wasn't able to reproduce your crash. In essence this achieves the same outcome as what you are doing, just a different way.

I certainly will try this method, and yes after the kids finish their homework...

I will report the results most likely in another 24 hours or so...

Status update:
The QoS method of limiting bandwidth seems to work.
Well it has been over 24 hrs without any reboots but when there is lots of traffic I get high ping times:
Reply from 192.168.x.1: bytes=32 time<764ms TTL=64
Reply from 192.168.x.1: bytes=32 time<805ms TTL=64
Reply from 192.168.x.1: bytes=32 time<954ms TTL=64

I am a bit concerned that configuring the throttle this way that will never be able to use my full bandwidth when I have not met the criteria of my daily limit.
Meaning I can only set the "FAST" rate to a percentage minus the "THROTTLE" rate. Both of which must add up to 100%
I can't upload any pictures today so cannot show you. I will upload them at a later date.