This is available in 1.2Sian wrote:Any news on binding the bittorrent traffic to one interface (I assume the fix posted above relates only to the webserver)? I'd really like to see this feature in the client, ATM only Vuze and rtorrent do support binding the torrent traffic to one distinct interface.
Thanks!
Bind to Interface or IP
Re: Bind to Interface or IP
Re: Bind to Interface or IP
Ok, didn't know that. Will try the client then asap. One additional thing, though. What happens if said interface goes down, does the traffic stop or does Deluge use another as fallback? Or is the behaviour configurable (like the Vuze option: "Enforce IP bindings even when interfaces are not available, prevents any connections if none of the specified interfaces are available")?andar wrote:This is available in 1.2Sian wrote:Any news on binding the bittorrent traffic to one interface (I assume the fix posted above relates only to the webserver)? I'd really like to see this feature in the client, ATM only Vuze and rtorrent do support binding the torrent traffic to one distinct interface.
Thanks!
Thanks a lot for the fast answer!
Re: Bind to Interface or IP
It appears that if the interface that you tell deluged to bind to is down, that it uses the working interface instead. I would like it to not do so, as I set up a VPN for my torrent traffic and would rather have no torrent traffic than torrent traffic that is not on my VPN.
deluged: 1.3.6
libtorrent: 0.16.13.0
deluged: 1.3.6
libtorrent: 0.16.13.0
Re: Bind to Interface or IP
Just registered here to say that I too would love to see this feature in Deluge. I can see that one is already able to bind to an IP address with Deluge on OS X (which is what I am using). But the two things that would make this feature perfect in Deluge would be:
The Transmission guys don't sound too interested in implementing this functionality in their standard build, was just wondering what the Deluge Team thinks about implementing the above in Deluge?
- Being able to bind to an interface name (e.g. "eth0", "ppp0" etc.) and have Deluge take care of binding to whatever the relevant IP address is at the time
Having the option to configure Deluge to only use the specified interface and not fall back to another available interface if the specified interface is down (I see this was logged as a feature request some time ago)
The Transmission guys don't sound too interested in implementing this functionality in their standard build, was just wondering what the Deluge Team thinks about implementing the above in Deluge?
Re: Bind to Interface or IP
Has there been any progress on this? I torrent over vpn and I need to ensure traffic doesn't leak outside of the vpn if the vpn gets disconnected.