Suggestion
Right now qBittorrent configures both listen_interfaces and outgoing_interfaces libtorrent options with almost the same configuration, and does not allow to configure them separately.
outgoing_interfaces
A list of names will be used to bind outgoing TCP sockets in a round-robin fashion
listen_interfaces
These are the listen ports that will be opened for accepting incoming uTP and TCP peer connections. These are also used for outgoing uTP and UDP tracker connections and DHT nodes.
If #24731 is implemented, it would be possible to use multiple interfaces, but all of them would be used for incoming and outgoing traffic.
I'd like qBittorrent to use two interfaces for incoming connections but only one interface for outgoing connections (for downloading).
Use case
I have a multihoming machine with multiple interfaces.
One network, a physical one, is fast and cheap but might be unreachable from some parts of the world due to government censorship.
Another network, a tunnel, is slower and more expensive, but reachable from everywhere.
I'd like to use the tunnel only for seeding, not downloading.
Extra info/examples/attachments
No response
Suggestion
Right now qBittorrent configures both
listen_interfacesandoutgoing_interfaceslibtorrent options with almost the same configuration, and does not allow to configure them separately.If #24731 is implemented, it would be possible to use multiple interfaces, but all of them would be used for incoming and outgoing traffic.
I'd like qBittorrent to use two interfaces for incoming connections but only one interface for outgoing connections (for downloading).
Use case
I have a multihoming machine with multiple interfaces.
One network, a physical one, is fast and cheap but might be unreachable from some parts of the world due to government censorship.
Another network, a tunnel, is slower and more expensive, but reachable from everywhere.
I'd like to use the tunnel only for seeding, not downloading.
Extra info/examples/attachments
No response