On 6/7/2012 1:03 PM, Tim Krieger wrote:
> Kind of branching off here but felt I should toss in my 2 cents re: 
> Throttling clients
>
> We have a similar problem where some remote clients have low bandwidth pipes 
> and we can't consume all available bandwidth.  Our environment is mostly 
> linux so and we achieve throttling using baculas client run before and client 
> run after options and some simple firewall traffic shaping scripts.
>
> Mac os may have the same/similar functionality available, if not, you can 
> always use the scripts server side to achieve the same(assuming a linux 
> storage server) just ensure some careful management and tweaking to prevent 
> collisions.

Thanks. I take it that only the marked packets hit the tc filter, and 
that for a server-side version the mark would be set in the INPUT chain. 
Wouldn't it then be possible to use both the client IP/port and the 
bacula server IP/port to set the mark so that only the client's Bacula 
traffic is throttled and everything else is not? That way, the iptables 
rules could be made permanent and the before and after scripts unnecessary.



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users