Need help understanding the announce URL #705
Replies: 1 comment 1 reply
-
Hi @aarondvail you don't need to apologize. We like having feedback from all users. In fact, yours it's a use case that I think it's very common. I've been thinking about making that process easier. ResponseThe params in the announce request (for the HTTP tracker) are described here: https://docs.rs/torrust-tracker/3.0.0-alpha.11/torrust_tracker/servers/http/index.html#announce and officially here: https://www.bittorrent.org/beps/bep_0003.html There are only three mandatory fields:
Corrent.
Correct.
It's the sha1 of only the
Currently not used. The tracker take the client's IP from the connection info. In the future, it could be a config option (to use this provided in the URL).
In a BitTorrent announce request, the fields "uploaded", "downloaded", and "left" play crucial roles in communicating the status of a peer within the BitTorrent swarm. Here's what each of these fields represent:
These fields are essential for the BitTorrent tracker to manage the swarm effectively. The tracker uses this information to decide which peers to connect for optimal distribution of the file, and also to keep track of overall swarm health and file distribution status.
It's the client's unique identifier. You can use any. The prefix is an abbreviation for the software you are using.
Spoofing the port in a BitTorrent context or in general networking can refer to sending packets with a forged source port number. While technically feasible in certain scenarios, it's important to understand the implications and limitations:
In summary, while port spoofing is technically possible, it has significant limitations in the context of two-way communication protocols like BitTorrent and is generally used for malicious purposes. Additionally, it's often detectable and can lead to legal consequences.
I suppose you want to seed those torrents. Since you have the complete file this should be
There are two types of response: normal and compact: Normal: {
"complete": 333,
"incomplete": 444,
"interval": 111,
"min interval": 222,
"peers": [
{
"ip": "105.105.105.105",
"peer id": "-qB00000000000000001",
"port": 28784
},
{
"ip": "6969:6969:6969:6969:6969:6969:6969:6969",
"peer id": "-qB00000000000000002",
"port": 28784
}
]
} Compact: {
"complete": 333,
"incomplete": 444,
"interval": 111,
"min interval": 222,
"peers": "iiiipp",
"peers6": "iiiiiiiiiiiiiiiipp"
} See https://docs.rs/torrust-tracker/3.0.0-alpha.11/torrust_tracker/servers/http/index.html#announce Other considerations
|
Beta Was this translation helpful? Give feedback.
-
Hello
First let me apologize for being a noob.
I need assistance with the announce URL for my private torrust tracker.
Here's a bullet list of what I'm trying to accomplish in a bash script.
Scan through organized folders (category/author/book as an example) {A simple bash script}
Create a torrent file per book {Using mktorrent}
Add created torrent file to private tracker (Using the post from How to use private tracker mode?)
And here's where I need help... identifying the different components of the URL: "http://0.0.0.0:7070/announce/U7K9EiczJp5uA8kUavaSMd63Jp4OaSxQ?info_hash=%81%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00&peer_addr=2.137.87.41&downloaded=0&uploaded=0&peer_id=-qB00000000000000001&port=17548&left=0&event=completed&compact=0"
http://0.0.0.0:7070/announce/ - IP/Port and announce to the tracker.
U7K9EiczJp5uA8kUavaSMd63Jp4OaSxQ - is the key as described in the aforementioned article. I use jq to parse the output to get just the key.
info_hash=%81%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 - I use sha1sum on the .torrent file to get this value, I'm not sure if that is the correct hash or not...
peer_addr=2.137.87.41 - I'm assuming this can be a bogus address
downloaded=0 - I'm assuming 0 is the desired number here
uploaded=0 - I'm assuming 0 is the desired number here as well
peer_id=-qB00000000000000001 - I have no clue what this is or what the value should be
port=17548 - I'm assuming this can be spoofed
left=0 - I have no idea
event=completed - are we sure?
compact=0 - again no clue
I'm hoping that I can get help on the ones I don't know and possible confirmation of my assumptions.
Once I get this and one other issue resolved, I'll right up a "how-to" if anyone wants it.
Beta Was this translation helpful? Give feedback.
All reactions