When changing network.bind_address.set at runtime, the listening socket is updated with the new address. However, dht still uses the old address, even after stopping and starting dht with dht.mode.set.
Steps to reproduce:
:::6881)network.bind_address.set=192.168.0.3dht.mode.set=off; dht.mode.set=onExpected result:
DHT should use the new address for the listening socket, i.e. 192.168.0.3:6881
Actual result:
DHT is still using the old address, i.e. :::6881
When binding to :::6881 this isn't a huge issue, but if you start rtorrent with a different network.bind_address and change it afterwards it breaks dht if the old address is no longer used.
The feature-bind branch aims at dealing with all these issues, which is going to take a while as I'm redoing a lot of the networking code.
I've once again actively working on this project, and donations would be appreciated.
Most helpful comment
The feature-bind branch aims at dealing with all these issues, which is going to take a while as I'm redoing a lot of the networking code.
I've once again actively working on this project, and donations would be appreciated.