[英]Where can I find a list of bittorent dht bootstrap nodes?
Using my google-fu I was able to find only a few nodes: 使用我的google-fu,我只能找到几个节点:
router.bitcomet.com, router.utorrent.com, router.bittorrent.com router.bitcomet.com,router.utorrent.com,router.bittorrent.com
Is there somewhere a list of all bootstap nodes which I'm not aware of? 是否存在我不知道的所有bootstap节点的列表? Where do the torrent client developers get addresses of the bootstrap nodes?
torrent客户端开发人员在哪里获取引导节点的地址? (I've looked at deluge source code and seen the modes above hardcoded.)
(我看过洪流源代码,看到上面硬编码的模式。)
so far i have got these. 到目前为止,我有这些。
session = lt.session()
session.listen_on(6881, 6891)
session.add_dht_router("router.utorrent.com", 6881)
session.add_dht_router("router.bittorrent.com", 6881)
session.add_dht_router("dht.transmissionbt.com", 6881)
session.add_dht_router("router.bitcomet.com", 6881)
session.add_dht_router("dht.aelitis.com", 6881)
session.start_dht()
Those are the only bootstrap servers I know of. 这些是我所知道的唯一的引导服务器。 Note that router.bittorrent.com is just an alias for router.utorrent.com.
请注意,router.bittorrent.com只是router.utorrent.com的别名。
uTorrent just uses router.utorrent.com as its bootstrap server, and I imagine most other clients do as well. uTorrent只使用router.utorrent.com作为其引导服务器,我想大多数其他客户端也会这样做。
If you have a specific client you're interested in know what it bootstraps off of, you can always wireshark its DHT traffic (from a fresh install) and see where its first DHT packet is sent. 如果您有一个特定的客户端,您有兴趣了解它的引导,您可以随时连接其DHT流量(从全新安装)并查看其第一个DHT数据包的发送位置。
If you have any torrents, the router is not very important, since you can also bootstrap off of normal bittorrent peers. 如果你有任何种子,路由器不是很重要,因为你也可以从正常的bittorrent对等体引导。
You initialise from a well known nodes as you mentioned above, ie "router.bittorrent.com:6881" 如上所述,您可以从众所周知的节点初始化,即“router.bittorrent.com:6881”
Then it's up to the DHT client to keep a track of nodes from thereon in. 然后由DHT客户端来跟踪其中的节点。
There is nothing stopping you from saving your routing table between sessions, though many of these nodes are likely not to be running the next day. 没有什么可以阻止您在会话之间保存路由表,尽管其中许多节点可能不会在第二天运行。
Since you're supposed to maintain the routing table, you may want to keep an eye on the nodes with the longest uptime and persist those between sessions. 由于您应该维护路由表,因此您可能需要关注具有最长正常运行时间的节点并在会话之间保留这些节点。
With my own tests DHT startup (until a reply to find_node, returns your node) is pretty quick from cold start. 使用我自己的测试DHT启动(直到回复find_node,返回你的节点)从冷启动开始很快。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.