Gargoyle Forum

Not sure if this is due to my retention of previous settings (Feb 9th Build) and flashing it. But this recent update seems to be working fine except for the qos_distribution.sh which is currently not rendering the charts at all regardless of the selection for time frame(s) for both up/down. If someo...

http://www.bufferbloat.net/projects/codel/wiki/Cake
http://www.bufferbloat.net/attachments/download/224

http://www.ntop.org/products/deep-packe ... tion/ndpi/
https://github.com/ntop/nDPI
https://github.com/heil/owrt-package/tr ... s-mod-ndpi

Could it also be utilized as a replacement for Layer 7 QOS functionality?

Just tested the latest build 1.7.1
Created a JailU and JailD and limited each at 200k max.
Created a quota of 10mb transfer total and throttle the IP into JailU/JailD.
Exceeded the quota, so I ran a speed test for ingress/egress.

Tested it, works perfect!

Just tested build : 1.7.X (Built 20150222-0823 git@5f5ddc4)
Results are the same as the original issue. Download quota throttle works, upload quota throttle broken. So it seems that the BB builds are yielding the same results.

Just another update. Flashed WZR-AG300-H with build : 1.6.X (Built 20141109-0020 git@f372e3b) Created a 10meg limit for both up/down quota for a single IP with a throttle applied for up/down traffic. (I created two throttled QOS rules to have the IP drop into) Ran speed test after quota was exceeded...

Tried similar config on WZR-AG300H router with the most recent build.
1.7.X (Built 20150109-0720 git@da35789)

Same results. Once quota is met, download does fall into correct throttle/queue. But upload is wide open.

Album collected on imgur.
http://imgur.com/a/bNGT3

Will be pulling the router and wiping configuration and testing again to see if it can be replicated.

An odd issue to which I am hoping someone may be able to shed some light. I have created two extra classifications being JailD and JailU. (one upstream and one downstream) Both of which are throttled down to 256k each (Max BW) and I have a quota rule set for an IP which is set for daily 850 megs tot...

Having a field available (50-60 characters in length) associated to the created rule to note/comment/reference what the rule is created for.