Rtorrent: DHT does not respect changes in network.bind_address

Created on 28 Aug 2019  路  1Comment  路  Source: rakshasa/rtorrent

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:

  • Start rtorrent with dht enabled
  • Check the listening socket used for dht (likely :::6881)
  • Change the bind address, e.g. network.bind_address.set=192.168.0.3
  • (Optional, has no effect) restart dht dht.mode.set=off; dht.mode.set=on
  • Check the listening socket again

Expected 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.

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.

>All comments

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Bystroushaak picture Bystroushaak  路  4Comments

frankvw2017 picture frankvw2017  路  3Comments

vinz243 picture vinz243  路  4Comments

mrvn picture mrvn  路  3Comments

legrostdg picture legrostdg  路  5Comments