You will have to make your own custom rules to address this issue. It is not a common scenario and the default rules that Gargoyle has will not address it. Per IP sharing can only help you if RDP and photo uploads are on different devices. I sense from your post that these are on the same device (the PC).
You will need to find a way to classify this photo upload traffic into its own class with lower percent bandwidth (like 10% for example). You will need to do this by the destination IP address of the Google Photos server. Use the connect list to identify the target IP address (or addresses) and use that to write your rule(s). You can CIDR format in your rule to specify a range of addresses which is probably what you will need to do. Google will be using more than one IP address most likely.
Once your rule is written test it by observing that traffic is correctly classified in the connection list.
Leave your upload bandwidth at 50% until testing is complete and everything is working. Then you can start to increase it until things break.
In your next post be sure to show the rules you have and your connection list.
QoS with a repeater and an unstable ISP
Moderator: Moderators
Re: QoS with a repeater and an unstable ISP
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Re: QoS with a repeater and an unstable ISP
Yes, it works a little better, but not much. RDP shows a second of delay (without QoS the delay can be 3-5")Volaris wrote:In the 600kbps graph above (last one) it seems to show QoS working. Are you still experiencing slow downloads/browsing when QoS upload is limited to 600kbps?
It's a big Cable company. I don't think they're messing with QoS. How can I find out?Volaris wrote:The other question I had was, what kind of ISP do you have? Is it a small wireless ISP? DSL? Cable?
I thought Google Photos was a VERY common program!pbix wrote: It is not a common scenario and the default rules that Gargoyle has will not address it.
Yes, but everyone on the net experiences slowdowns. Also when my phone backups media everything starts to crawl...pbix wrote: I sense from your post that these are on the same device (the PC).
If I'm not mistaken Google (like Facebook) use a VERY big pool of IP addresses and the IP are not all contiguous, and also change over time (have in mind that gPhotos works with most Android phones and millions of PCs so the traffic must be kind of mind blowing.pbix wrote: You will need to do this by the destination IP address of the Google Photos server. Use the connect list to identify the target IP address (or addresses) and use that to write your rule(s). You can CIDR format in your rule to specify a range of addresses which is probably what you will need to do. Google will be using more than one IP address most likely.
I'll try with your suggestion but I have little faith...
I don't have any special rule, only the ones that came with Gargoyle. I'll post the connection list later when everyone is asleep so the list is smaller.pbix wrote:In your next post be sure to show the rules you have and your connection list.