Code: Select all
------------------------------------------------------------------
| _____ _ |
| | __ \ | | |
| | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
| | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
| | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
| \____/\__,_|_| \__, |\___/ \__, |_|\___| |
| __/ | __/ | |
| |___/ |___/ |
| |
|----------------------------------------------------------------|
| Gargoyle version 1.5.9 | OpenWrt Attitude Adjustment branch |
| Gargoyle revision f73df29 | OpenWrt revision r34879 |
| Built January 03, 2013 | Target ar71xx/default |
------------------------------------------------------------------
Code: Select all
root@OpenWRT - Gargoyle:~# cat /proc/cpuinfo | grep system
system type : Atheros AR7161 rev 2
Code: Select all
root@OpenWRT - Gargoyle:~# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 2.8M 324.0K 2.4M 12% /
/dev/root 2.5M 2.5M 0 100% /rom
tmpfs 30.2M 268.0K 29.9M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock4 2.8M 324.0K 2.4M 12% /overlay
overlayfs:/overlay 2.8M 324.0K 2.4M 12% /
Code: Select all
[Classification Rules]
Match Criteria Classification
Destination: 50.93.246.0/23,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination: 50.93.255.0/24,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination: 209.208.232.0/23,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination: 209.208.241/24,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination: 209.208.242/28,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination: 209.208.250/24,
Destination Port: 443, Connection bytes: 1024 kBytes Bulk
Destination Port: 80, Connection bytes: 1024 kBytes Normal
Destination Port: 443, Connection bytes: 1024 kBytes Normal
Destination Port: 88, Connection bytes: 1024 kBytes Normal
Destination Port: 3074, Connection bytes: 1024 kBytes Normal
Destination Port: 80 Priority
Destination Port: 443 Priority
Destination Port: 53 Priority
Destination Port: 88 Priority
Destination Port: 3074 Priority
Destination Port: 4289 VoIP
Destination Port: 1863 VoIP
Code: Select all
Class Name Percent BW Min BW Max BW Load (kbps)
VoIP 1% 80 nolimit 0.0
Priority 70% zero nolimit 4
Bulk 5% zero nolimit 4026
Normal 24% zero nolimit 0.7
I am using a cloud backup service and utilizing QoS Upload rules to limit the impact it has on my browsing. I set rules for QoS upload for ranges of IP addresses (the cloud backup server IPs), on a specific port (443, HTTPS), and connection bytes reach 1024 kB. With this rule, I assigned the traffic to a low % class (Bulk).
The rule works fine until a connection sends over 4GB of data. At that point, QoS appears to ignore either of my rules pertaining to port 443 and connection bytes 1024 kB. Instead, I end up with all the traffic for upload and download in the Priority class, which is the highest % allocation. This is what I was trying to avoid.
It looks like you can't set Connection bytes higher than 4GB (4194303 kB), which would correspond to the max value of an unsigned 32-bit integer. Either way, should I expect to see the QoS rule be able to handle a connection of this size? Or should I rewrite my rules to work around it?
Expected behavior: Connection remains Bulk class after reaching 4GB
Observed behavior: Connection changes to Priority class after reaching 4GB
Also, I'm unsure whether this happens with QoS download. This backup application seems peculiar in how long it holds a connection compared to my other applications using download.
I'm finding Gargoyle to be very powerful. Just trying to tune my setup. Thanks for all the hard work.