mhertz wrote:Still a manpower/volunteer issue I think.

Is it possible to add the tag 2.0.4 in the current github master branch? This will at least create the release tarball.
Does this require additional work?

There's plenty of useful bug correction after 2.0.3. One of which avoids a startup crash...
It would really be useful to release an official 2.0.4 to include those.
Some downstream clients rely on github tarballs to upgrade, please consider it.

I'd enjoy having already merged bugs released... Example: https://forum.deluge-torrent.org/viewtopic.php?f=8&t=55767 My theory: the other great open source contender based on libtorrent rasterbar, qBitTorrent, is getting so good now, that everybody's loosing interest in deluge. It's a shame beca...

Hello, is it possible to create package 2.0.4 with just the changes already on the develop branch? The bug I need is already corrected https://github.com/SynoCommunity/spksrc/pull/4153 I need that to upgrade the syno community package for deluge https://github.com/SynoCommunity/spksrc/pull/4153 But ...

I just re-read the docs https://www.libtorrent.org/reference-Settings.html
All is fine:
- listen_interfaces is used for both in/out uTP and tracker, and for incoming TCP
- outgoing_interfaces is used only for outgoing TCP

Both parameters need to be consistent to muti-home properly.

Thank you. I will test a bit more with the outgoing interface stuff. In principle I know how it works, because stuff like squid, dnsmasq, and the like need this to properly multi-home in some situations. However from the lib torrent documentation, Arvid writes that it's only used for outgoing TCP co...

I contributed a PR with a change doing this with the regular deluge network options:
https://github.com/deluge-torrent/deluge/pull/300

I don't think there's a ticket for that yet, so if you can provide it will be much appreciated.

Thanks, I will test along your suggestions regarding the interface names. For the moment I'm stuck with version 1.3.14, for which this don't work. When I manage to get 2.0.x to run correctly, I will test it. Regarding LT config I think that the listen_interfaces libtorrent parameter is not managed: ...

Hello, I run deluge on a linux "big storage" box with several ipv4 addresses. Deluge listen interface is set to one of the box local ipv4, e.g. 10.3.14.15 My internet router has VPN connections, and I route the deluge box through the VPN via ipv4 10.3.14.15. This works fine, all deluge tra...