| | 1 | = IfaceWatch = |
| | 2 | |
| | 3 | Watch for IP changes on specific interfaces and notify libtorrent. |
| | 4 | |
| | 5 | [[PageOutline(2-4,,inline)]] |
| | 6 | |
| | 7 | == Current features == |
| | 8 | |
| | 9 | * No WebUI support |
| | 10 | * Works only on Unix based hosts (limitation of [https://github.com/bat-serjo/PyIface PyIface]) |
| | 11 | * It runs on the daemon, so it will work well in a daemon/thin client setup. |
| | 12 | |
| | 13 | == Links == |
| | 14 | |
| | 15 | * [https://github.com/bendikro/deluge-iface-watch/releases Download] |
| | 16 | * [https://github.com/bendikro/deluge-iface-watch#changelog Changelog] |
| | 17 | |
| | 18 | == Getting started == |
| | 19 | |
| | 20 | === Download === |
| | 21 | |
| | 22 | Download IfaceWatch from the [https://github.com/bendikro/deluge-iface-watch/releases]. |
| | 23 | |
| | 24 | You must download the egg that matches your python version (Python 2.6 or 2.7). See [http://dev.deluge-torrent.org/wiki/Plugins#InstallingPlugins] for details if you are unsure. |
| | 25 | |
| | 26 | === Installing the plugin === |
| | 27 | |
| | 28 | The plugin egg file can be installed through the Deluge GTKUI, or it can be installed manually. |
| | 29 | |
| | 30 | See [http://dev.deluge-torrent.org/wiki/Plugins#InstallingPlugins instructions for how to install] |
| | 31 | |
| | 32 | If you run Deluge in non-Classic mode (daemon and client setup), take a look at [http://dev.deluge-torrent.org/wiki/Plugins#Client-ServerSetups Running a server/seedbox with a Deluge daemon] |
| | 33 | |
| | 34 | === Configuring IfaceWatch === |
| | 35 | |
| | 36 | When enabling the plugin in Deluge a new tab is created in the Deluge prefences for IfaceWatch. |
| | 37 | The settings allows specifying a network interface, such as *eth0*, to be |
| | 38 | monitored for changes at the interval specified in the setting. |
| | 39 | |
| | 40 | In a VPN scenario where you want only the torrent traffic to pass through the VPN interface |
| | 41 | it is necessary to manually set up routing table rules for this traffic. When the IP changes for |
| | 42 | an interface, IfaceWatch will only instruct Deluge to change the IP that libtorrent listens on. |
| | 43 | Therefore it is necessary to adjust the routing table rules as well when the IP changes. |
| | 44 | |
Deluge
