Setting up QoS for Backblaze on a Trendnet router

I am not a networking expert so I am in over my head a bit on this topic. I have Backblaze running on my home system, and I want to use the QoS in my Trendnet AC1750 router to give the Backblaze bandwidth lower priority than most other traffic. What has me stumped is what Backblaze says their IP's are and how to input that information into the Trendnet router.

Backblaze lists their IP's on the following webpage:
https://help.backblaze.com/entries/20202037-what-ip-addresses-does-backblaze-use

I have a shaky understanding of "subnet notation", but from what I can tell, saying 208.87.220.0 /24 is another way of saying the range 208.87.220.0 - 208.87.220.255. Hopefully I have that correct.

Next, I'm trying to input the IP's listed on that webpage into my Trendnet AC1750 router's QoS settings, and set it at "low" priority class. However, from what I can tell, I can only specify a single IP address per QoS entry. In other words, it won't let me say either "208.87.220.0 /24" or "208.87.220.0 - 208.87.220.255", and will only accept something like "208.87.220.0".

Am I doing something wrong, or is the QoS of my router just that limited in capability?

QoS settings are based on the source IP (your Backblaze box) not the other way around
//Danne

Do the filtering based on the port of the traffic, rather than the IP.

QoS only affects outbound traffic, but the router allows you to specify either a source or a destination IP for doing it. I don't want to lower the priority for all the traffic from that computer, only the Backblaze application, so priority based on source IP is a bad idea.

Priority based on ports accomplishes nothing, because backblaze uses port 443, the same as HTTPS. The whole point is to give web traffic higher priority than Backblaze.

Therefore, priority based on the destination IP would seem to be the the correct approach.

Can anyone help?

Does it not have a usage limit within the software? Really hate these "cloud" backup services that don't put two shits into there software. It's consumer grade gear, so yeah it doesn't surprise me you're going to have a tough time doing entire subnets like what you want without the aid of 3rd party firmware.

The way you're trying to do QoS isn't the way they are intending on it being used. Mostly it's to prioritize bandwidth on your internal network as a whole or on a specific machine maximizing your most important traffic. Software that rides the port 80/443 really make it a pain in the ass to control.

That's annoying, they should have the option of using a different port to make it easier to manage.

Have you tried adjusting the throttle option?

I don't see any way to set up the QoS the way you want with the stock firmware. DD-WRT supports that device, maybe you could get better results with that? It supports prioritizing by IP range, so you could enter the rules for the Backblaze servers easily.

I decided to go with a workable if not quite perfect solution: I set low priority for traffic from that machine's MAC address that is on port 443. So any HTTPS from that machine will also get low priority... but that's better than Backblaze crowding out other traffic.

There is a throttle setting in Backblaze, but I'd it to use all the free bandwidth that's left over by using QoS.

Setup a local backup server that then uploads to Backblaze and set the priority based on that server's internal IP. This would also allow you to use this server for other cloud service syncing or perhaps even backing up online server/sites to it.

The machine running Backblaze is my home server already -- it runs all sorts of applications, is a file server, and PVR -- so I can't set all the traffic from the machine to low priority, but limiting the port 443 traffic from that machine is acceptable.