On Tue, 21 Dec 2021, Alexander V. Makartsev wrote:
On 21.12.2021 20:51, Mattias Wadenstein wrote:
This is odd, because many other torrent trackers and hundreds of torrents
work just fine.
I don't know how to check if it is working. A plain simple 'wget' request
gives:
$ wget -O- http://bttracker.debian.org:6969/announce
--2021-12-21 23:32:43-- http://bttracker.debian.org:6969/announce
Resolving bttracker.debian.org (bttracker.debian.org)... 130.239.18.158,
2001:6b0:e:2018::158
Connecting to bttracker.debian.org
(bttracker.debian.org)|130.239.18.158|:6969... connected.
HTTP request sent, awaiting response... No data received.
Retrying.
And if I send same request to another tracker I get.. well at least
something:
$ wget -O- http://tracker.humblebundle.com:2710/announce
--2021-12-21 23:39:44-- http://tracker.humblebundle.com:2710/announce
Resolving tracker.humblebundle.com (tracker.humblebundle.com)...
104.154.156.79
Connecting to tracker.humblebundle.com
(tracker.humblebundle.com)|104.154.156.79|:2710... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-12-21 23:39:47 ERROR 404: Not Found.
I get the first behaviour with wget. You could something that doesn't
actually exist, like /stats or something that does, like /stats?
Could it be that Debian torrent tracker blocks out requests from Tor
network?
Not as far as I know. But I guess if that particular exit node had been
particularly nasty in the past, there might be filters upstream from it.
/Mattias Wadenstein
