Remove non-working DHT bootstrap nodes #21296
Conversation
|
I tested the addresses using qBit 5.0. Run qBit. |
|
I have different results. Tested your setup and all nodes separately.
|
|
Are you sure you got the nodes exactly from those bootstrap domains? |
|
Yes.
|
|
Is it definitely a clean install? Just to make sure, could you test dht.libtorrent.org with the wrong port number? |
No, it's my working client.
Hmm, it still manages to get DHT nodes somehow. Despite all transfers stopped. That's why I asked for reliable testing methods. I guess I need to wrap up a new isolated client with incoming ports closed. |
|
Yeah, running with closed port prevents bootstrapping (DHT: 0) from any of But it would be good to have an easier method to check their accessibility. |
router.utorrent.com has been dead for a long time. router.bittorrent.com died about a month or two ago. dht.aelitis.com doesn't work either. It is no longer possible to get DHT nodes from them. Added router.silotis.us. Only ipv6!
stalkerok
force-pushed
the
bootstrap-nodes
branch
from
e802d5f to
8a27a72
Compare
|
Added router.silotis.us. Only ipv6! |
Where does it come from? How can we be sure that it is safe? |
I found it from another torrent client, I understand the owner is https://github.com/ssiloti |
|
So is it confirmed that such DHT bootstrap nodes are dead and not just inaccessible to some people? |
|
They don't work for me, either through a VPN or from my home connection. |
|
FYI for testing: You gain entrance to the DHT network if you somehow connect to at least one node. Then that node can help you find other ones until you position yourself with the closest nodes to you. This single node can be obtained:
|
No. At least not configured to do that in qBittorrent. We always start with 0 nodes. |
|
Add |
|
I would also add |
They don't work. |
|
Can this be merged and added to the backport to 5.0? |
|
Is there any forum/reddit discussions etc. about these DHT nodes being actually dead.....dead?? |
|
This is probably not discussed anywhere and users don't know how to test it properly. They connect to the DHT through other sources and don't notice anything. First screenshot: home connection, second: VPN. VPN is ipv4 only. 2 You can check their working order yourself. |
|
Can anyone confirm or deny the workability of these addresses by running the correct tests? Or merge the PR. |
|
I made a script. Nmap should be installed. Requires root because of #!/bin/bash
set -euo pipefail
if ! command -v nmap > /dev/null; then
echo 'Nmap should be installed!'
exit 1
fi
if ((EUID != 0)); then
echo 'Need to be run as root!'
exit 13
fi
LIST=(
'dht.libtorrent.org:25401'
'dht.transmissionbt.com:6881'
'router.bittorrent.com:6881'
'router.utorrent.com:6881'
'dht.aelitis.com:6881'
'router.bitcomet.com:6881'
'dht.libtorrent.org:6881'
)
# https://www.bittorrent.org/beps/bep_0005.html#ping
PAYLOAD='d1:ad2:id20:abcdefghij0123456789e1:q4:ping1:t2:aa1:y1:qe'
scan() {
nmap -sU -oG - "${1%:*}" -p "${1#*:}" --data-string "${PAYLOAD}" 2> /dev/null | grep -q '/open/'
}
for a in "${LIST[@]}"; do
if scan "${a}"; then
echo "${a} => WORKING!"
else
echo "${a} => DEAD"
fi
doneMy results: P.S. |
What i got too when i tested each node individually in qbit ~20 min+ each, no torrents, a few days ago. I didn't say anything because i don't know how reliable this test was. |
|
@glassez |
I have nothing to say about this. You can continue without my approval. |
|
@stalkerok |
|
Forgot to say. I didn't test |
|
Hello everyone I switched to qBittorrent some time ago in early September precisely due to the fact that DHT stopped working in uTorrent. And although now I have already transferred everything to qBittorrent and have already got used to it and I probably do not plan to return back to uTorrent. However, I still have uTorrent installed and periodically checked. So, the other day, DHT started working again in uTorrent. So at least one of the nodes that are used for DHT in uTorrent (which I do not know and do not know how to look at and check it in uTorrent) came to life the other day (about which I also met a message from one of the users on one of the torrent trackers, according to him router.utorrent.com It still doesn't work, but router.bittorrent.com suddenly came to life). So in my opinion, it's worth double-checking this again before making the changes discussed here to qBittorrent for everyone already in a public release. Even if something doesn't work for a long time, as this example shows, it can suddenly start working again. Therefore, I personally do not understand, to be honest, why remove something from qBittorrent, even if it does not work now, then at some point it may well work again. How does it interfere if it exists but does not work? Well, it doesn't work and it doesn't work. And if that happens, not all users will be able to figure out how to return what and where manually, and in general, not all users will know about it. Therefore, personally, if I were in the place of those responsible for this, it would be better to double-check everything once again and think again before making such changes and deleting something from the qBittorrent settings for all users by default. Moreover, it cannot be excluded that the situation with the availability of nodes for DHT may differ from one user to another, including depending on the country and/or even a specific provider. PS: if anything, please excuse me, maybe I don't understand all this enough from a technical point of view, and besides, I don't know English, and I use an online translator to write and read such messages. |
Yeah, that appears to be true.
This change was unnecessary from the start, yes. Noone had strong objections though.
We always can add it back. Nothing critical here. |
|
If router.bittorrent.com remains working until 5.1.0 is released, I may add it again. |
|
@HanabishiRecca @stalkerok OK. My task was to write about it here and draw attention to it. |
|
Two months ago I decided to look for more DHT bootstrap nodes, and I found something. I've been tracking them and they work good. The author of the first one also has a profile on github https://github.com/h4cc Before 5.1.0 comes out I want to bring back the removed |
I'm ok with it.
I think not. We should only use sites with reputation and not just any site available on the web. I would actually vote to remove |
I suggest ask him about it. @ssiloti You don't mind using this node? |
I spun that server up years ago to bootstrap the IPv6 DHT when support was first added to libtorrent. I wouldn't recommend adding it to qBittorrent. It's on a tiny VPS so it probably can't handle the amount of traffic qBittorrent would send and I make no guarantee it will stay up long term. |
@stalkerok OK. Great. I support this. That's what I've been talking about since I started participating in this discussion. :) UPDATE: @stalkerok Are you sure you don't mean |
@Chocobo1 I agree with that. |
@stalkerok Are you sure you don't mean |
|
I meant |
@stalkerok OK. Clear. Thank you for your explanation. But maybe then you'd better fix the mistake in that comment. |
|
Are these nodes good?? = |
Discussion: #21296 (comment) #21296 (comment) PR #22081.
|
just FYI |
router.utorrent.com has been dead for a long time. router.bittorrent.com died about a month or two ago. dht.aelitis.com doesn't work either. It is no longer possible to get DHT nodes from them.
Added router.silotis.us. Only ipv6!