Re: [Duplicity-talk] Binding duplicity to dedicated IP/network interface

[edgar . soldin]

On 16.04.2019 12:32, Jansen, Willem via Duplicity-talk wrote:
> Dear friends of duplicity,
>
> quick question I could not find a straight-forward answer to despite a longer 
> search:
>
> Situation:
> * Have Server, runs duplicity for backup, uses trickle to keep upload at bay
>
> Complication:
> * Router is able to prioritize traffic - better than the static trickle 
> solution - but can only differentiate on src/dst IP and port, but both are 
> not suitable to identify duplicity traffic
>
> Idea for solution:
> * Get 2nd internal IP address for dedicated (virtual) interface
> * Bind duplicity to dedicated interface
> * Throttle traffic on router, discriminate by src IP
>
> .. but that hinges on binding duplicity to a dedicated IP. Any idea how to do 
> that? Search revealed something about namespaces and the 'ip' command, but is 
> there a more obvious solution available?
>

hey Willem,

how about this
  
https://unix.stackexchange.com/questions/210982/bind-unix-program-to-specific-network-interface
?

..ede/duply.net