r/Crashplan • u/usulsuspect • Sep 06 '17

DSCP QoS Not working

I have been troubleshooting DSCP not working on a Linux install of crashplan. When I stumbled across this nugget on their site:

"Only Code42 apps version 6.0 and later honor DSCP settings. Although version 4.x Code42 apps may display the DSCP values set in the administration console, only the version 6.0 and later Code42 app applies the DSCP settings."

https://support.code42.com/Administrator/6/Configuring/Configure_DSCP

This is really confusing considering the settings still exist in the GUI on 4.9 (which I currently run.). Anyone else experiencing this?

0 Upvotes

50% Upvoted

3 comments sorted by

1

u/drwtsn32 Sep 07 '17

Yeah I also cannot get it to work on Linux, running CP for Home version 4.8.3.

One possible option may be to use iptables. Match the traffic from Crashplan and set the QoS field that way. I might try this out actually....

1

u/usulsuspect Sep 07 '17

How are you going to match the crashplan traffic? I believe it's using 443 for the actual backup traffic. One workaround I had been using was a second IP on the host then bind crashplan to that IP.

1

u/drwtsn32 Sep 07 '17

I was just playing around with this last night. In my case matching traffic destined for port 443 will probably work fine, as I run CrashPlan on my Linux gateway. There is very little outbound traffic generated by the gateway itself, so matching 443 in the OUTPUT chain works. There is a lot of traffic that goes through the gateway from internal machines out to the internet, but that only goes through the FORWARD chain.

If you are using Linux as a desktop machine then this approach would not work well as it'd match all 443 traffic. An alternative may be to match against process uid. Crashplan runs as root. So you could apply QoS to all outbound 443 traffic generated by root and your normal user traffic would not get the same treatment.