Skip to content
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

Peer IP 0.0.0.0 #8361

Open
teddyrogers opened this issue Dec 28, 2024 · 5 comments
Open

Peer IP 0.0.0.0 #8361

teddyrogers opened this issue Dec 28, 2024 · 5 comments

Comments

@teddyrogers
Copy link

I came across these entries in the peer list and I could not find any information that specifically explained what they are. I make the assumption peers on 0.0.0.0 are part of the internal Tribler network?

image

@qstokkink
Copy link
Contributor

These are classic web servers (HTTP/FTP) that have the same files as the torrent. They can also be part of a torrent's swarm. This has been part of the BitTorrent protocol specification since 2008, but it is quite rare to actually see this feature used (in my experience). So, there is nothing wrong: it's just rare to see torrent creators use this.

You can read more about what these are here: https://www.bittorrent.org/beps/bep_0017.html, https://www.bittorrent.org/beps/bep_0019.html .

@teddyrogers
Copy link
Author

Thank you for the info. I was querying specifically IP address 0.0.0.0, if this is not related to the internal Tribler network, should the peer IP, instead, reference the HTTP/ HTTPS of the webseed server IP it is connected to?

@qstokkink
Copy link
Contributor

I guess my answer is: yes and no. We receive this IP info from our underlying torrent library. Yes, it would be nice if the IP matched the URL and I think the info can be easily gotten from the direct connection. However, my "no" is that the code to directly access the connection is hidden in our torrent library's C code and we can't freely modify this.

Long story short, I think the only reasonable solution would be to fix this inside our underlying torrent library. However, the release cycle for that library is quite long so I don't expect this to get either fixed or make its way into a release any time soon. It would be too optimistic to schedule this issue for an upcoming release but we can keep this in mind for the long term.

@teddyrogers
Copy link
Author

teddyrogers commented Jan 7, 2025

@qstokkink it would be good if there were some visibility on the IP address being connected to. Take "@mirror.yandex.ru" as an example, in a browser this is URL https://mirror.yandex.ru, for me this points to server 213.180.204.183. There may be load balancing active to deliver the same content from a local/ regional content delivery network.

@qstokkink
Copy link
Contributor

Just to clarify: I think you make a good point and I like your idea. I just wanted to do some expectation management: this is hard to implement due to our technology stack and (even optimistically) it will take a while before this feature can make its way into Tribler.

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

No branches or pull requests

2 participants