Thought about the feature.

In the relatively old but powerful qBittorrent client, I can still define only one network interface and binding address for each IP protocol. What about rqbit?

Since this project is relatively new, I believe that multi-interface defining would also be useful, for example:

• Mycelium
• Yggdrasil
• CJDNS
• Some VPN 1
• Some VPN 2
• Internet IPv4
• Internet IPv6

This option requires multi-network binding and the spawning of announcement threads. The subject is not trivial in the implementation also, I understand; qBittorrent can only work with one selected interface at a time. Additionally, while qBittorrent supports IPv4 and IPv6 binding (2 threads) out of the box, there is no option to define multiple (2+) external IPs. It auto-resolves only one announcement address for IPv4 and one for IPv6. If I use Internet, Yggdrasil, Mycelium, and CJDNS, it will always detect only one of them (as the IPv6) and skip announcements for the other networks.

I believe a modern client should be able to handle multiple networks. It would be a nice feature in a world where torrent usage has become restricted, and local / mesh networks could help with that. But the problem, there is too many networks, and one client. Running a new separated client process for every network is not good for performance reasons.

Thank you.