Today I turned on a backup of one of my lager directories to send them to CrashPlan. About 5 minutes into it my browser of the internet slowed to a crawl due to upstream congestion. I paused CrashPlan and everything returned to normal.
With a little experimenting I noticed that the adaptive QOS identified the traffic as "General" when you clicked on the host icon. It appears that the adaptive QOS puts it in the same category as web browsing but I can't be sure other than my anecdotal evidence of making phone calls and steaming video still worked fine with CrashPlan enabled. CrashPlan seems to be using ports in the 5000's to do it communicating. I am attaching a picture of the traffic page.
When I ran tomato I was able to leverage the DSCP bits of CrashPlan to have it set to file transfer priority. How can one communicate to Trend Micro that their QOS rules don't account for CrashPlan? Also has anyone found a way to modify the TC rules to account for DSCP bits in Merlin/ASUS firmware's?
With a little experimenting I noticed that the adaptive QOS identified the traffic as "General" when you clicked on the host icon. It appears that the adaptive QOS puts it in the same category as web browsing but I can't be sure other than my anecdotal evidence of making phone calls and steaming video still worked fine with CrashPlan enabled. CrashPlan seems to be using ports in the 5000's to do it communicating. I am attaching a picture of the traffic page.
When I ran tomato I was able to leverage the DSCP bits of CrashPlan to have it set to file transfer priority. How can one communicate to Trend Micro that their QOS rules don't account for CrashPlan? Also has anyone found a way to modify the TC rules to account for DSCP bits in Merlin/ASUS firmware's?
Attachments
Last edited: