duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jansen, Willem
Subject: [Duplicity-talk] Binding duplicity to dedicated IP/network interface
Date: Tue, 16 Apr 2019 12:32:54 +0200

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?

  Best,
   Willem


reply via email to

[Prev in Thread] Current Thread [Next in Thread]