#Bitcasa user manual windows

You can set the tags and the sniffer will actually show the tags but what comes out the port does not have tags.

#Bitcasa user manual windows

I am not sure it is on all versions of windows but it appears microsoft removes any form of packet markings on the client versions of their OS. The selection of the traffic is the easy part it it actually applying the limits that would require the special router software.

You are now just matching a packet tag rather than a IP address or a port number or something. You would still need all the traffic limitation stuff in the router. The actual tagging of packets is a waste of time mostly. There is no scheduled QoS on my router either (though it respects QoS tagging), so that isn't an option. Google reveals nothing for Windows - only high-end routers from Cisco etc. I cannot see a way of doing this in the QoS policy editor, and it's looking like some sort of scheduled script may be in order, but I thought I'd ask in case there is a 'proper' way of doing this.

What I really would like, is to automatically change the QoS policy between 1am and 5am so that Bitcasa has no limits applied. I am mirroring a large amount of data to Bitcasa (over 2TB), and need that to happen as fast as possible without triggering the rate caps.Īt the moment, I have bitcasa limited to 160Kbps, which is a safe speed to run 24/7 without triggering the rate caps and still allows normal use on top, but obviously progress is slow at this rate. The reason is that I am using Virgin Media as my ISP, and they have a traffic management policy. As the subject suggests, I want to vary my QoS policies on my server according to the time of day.