Skip to content

BT DHT does not respect the client_bind_address setting #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Shot2 opened this issue Feb 17, 2025 · 0 comments
Open

BT DHT does not respect the client_bind_address setting #129

Shot2 opened this issue Feb 17, 2025 · 0 comments

Comments

@Shot2
Copy link

Shot2 commented Feb 17, 2025

MLDonkey built from 3.2.1 release source, enabling (among others) the BT protocol. Running under Debian 12.

The setting "client_bind_addr" (used for P2P client connections) is set by myself as 10.46.46.5. Things work as expected, but for one thing.

Short excerpt from 'netstat -puant' for mlnet:

udp        0      0 10.46.46.5:14663        0.0.0.0:*                           75004/mlnet
udp        0      0 10.46.46.5:14664        0.0.0.0:*                           75004/mlnet
udp        0      0 0.0.0.0:14665           0.0.0.0:*                           75004/mlnet
udp        0      0 10.46.46.5:14666        0.0.0.0:*                           75004/mlnet

As can be seen, the various P2P services in use respect the setting and properly bind to 10.46.46.5 ... except for the BT DHT service (configured by myself to use UDP port 14665), which here incorrectly binds to 0.0.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant