Gargoyle itself only shows up in BW monitor half the time

Report issues relating to bandwith monitoring, bandwidth quotas or QoS in this forum.

Moderator: Moderators

Post Reply
moeburn
Posts: 33
Joined: Mon Aug 19, 2013 4:43 pm

Gargoyle itself only shows up in BW monitor half the time

Post by moeburn »

So I'm running Transmission on my WNDR3700v2, which is running Gargoyle v1.5.10. Since Transmission doesn't have any bandwidth graphs, I like to use Gargoyle's built in BW Monitor.

But when I click on Bandwidth Usage, then sort by hostname, there are TWO entries for "Gargoyle"! Sorting by IP address, there are two entries for 192.168.1.1! They both show the exact same data. Sometimes they work, and they show the same bandwidth usage that the Transmission web UI shows. And then suddenly they'll just stop working, and they will only show a tiny fraction of what Transmission is using. IE, if Transmission was downloading at 100kB/s, and slowly increased to 500kB/s, the BW Usage graph for Gargoyle/192.168.1.1 will show a download graph that shows bandwidth went from 1kB/s to 5kB/s (same thing in Total Bandwidth graph for this particular IP). If I sort by "Total Bandwidth" (for the entire WAN), I can correctly see the Transmission bandwidth usage.

Gargoyle doesn't show up at ALL in the B/W Distribution page (well there is an entry for Gargoyle, but it shows 0 bytes, at all times. Even when the Bandwidth Usage graph is reading correctly).

I also have QoS rules set to deprioritize any traffic sourced from, or destined to, 192.168.1.1; I have Gargoyle's IP set to 'slow', and everything else to default to 'fast'. When the BW Usage graph is working, so is the QoS; I can see the Transmission bandwidth in both the hostname Gargoyle, and the QoS Download Rule "slow". But then all of the sudden, the BW Usage graph will stop correctly reporting the bandwidth that Transmission is using, and if I sort by QoS rules, said bandwidth shows up in the "fast" rule.

So the bandwidth usage and QoS systems are having a hard time keeping track of just who exactly Gargoyle is! It probably has something to do with the fact that I have two entries for Gargoyle in the list. Even immediately after a reboot.

I'd love to try using the reset button to reset all my settings, but I can't; Gargoyle seems to ignore the reset button. It worked fine on other firmwares, but when I try a 30-30-30 reset on Gargoyle, it doesn't reset my settings.

moeburn
Posts: 33
Joined: Mon Aug 19, 2013 4:43 pm

Re: Gargoyle itself only shows up in BW monitor half the tim

Post by moeburn »

Aaaanybody? I've tried everything I can think of. It was working fine before! When I only had 1 entry for "Gargoyle" in the BW Monitor graphs, the QoS settings for source/destination of 192.168.1.1 worked fine! Now that there are 2 entries for Gargoyle/192.168.1.1 in the graph, all the traffic sourced from / destined to 192.168.1.1 is being set to the default "fast" QoS rule.

I've even tried setting rules for the port that Transmission is using, but no luck. I checked the 'connections' page, and there are entries for "Gargoyle:51813" set to the "Fast" QoS rule! Yet both my QoS pages have told any traffic sourced from, or destined to Gargoyle, should be set to the 'Slow' rule.

And it was working fine before...

moeburn
Posts: 33
Joined: Mon Aug 19, 2013 4:43 pm

Re: Gargoyle itself only shows up in BW monitor half the tim

Post by moeburn »

Here! I caught it happening! Gargoyle was being limited by QoS for the first couple of minutes, then in MID-DOWNLOAD, it switched over to not being limited by QoS, and its traffic disappeared from the bandwidth monitor!

Here is the total bandwidth for IP address 192.168.1.1 (there are two entries in the list for 192.168.1.1, but they both show the same graph):
Image

And here is the router's total bandwidth:
Image

All this was when there was absolutely no other devices even connected to the router, except for my linux laptop to view the graph, and i made sure it had no net traffic of its own.

So the traffic starts out being designated as hostname 'gargoyle', then for some reason it just disappears, won't show up under ANY hostname, and only shows up under 'total bandwidth'. Whatever is causing this issue is likely also the cause of the QoS issue; after all, QoS can't limit traffic to 192.168.1.1 if the traffic supposedly isn't going to 192.168.1.1

Post Reply