But how about php-based trackers, like PHPBT? I got a weird torrent that has PHPBT as a tracker. It has a tracker URL which looks something like http://tracker.com/track/tracker.php/announce
. I can't seem to get any remote connections when I'm on this torrent. I suppose adding a port number to the tracker URL wouldn't fix anything? (I got a funny feeling that it will make the tracker unreachable; the 6969 port on this server seems closed)
I wonder if this has anything to do with the "Nat checking is disabled." disclaimer on the torrent download page...I'm on a NAT (yes, I've opened the 6881, etc ports
), and this feature, as said by DeHackEd, does the following:
"Clients will only be given IP addresses of clients with forwarded ports. In theory, you should be able to connect to each peer on the list."
BTW, about the transparent http proxy thing, I've found that because the proxy acts as a "messager" between the user's pc and the internet, the proxy is sometimes mistaken as the user's pc, and its IP address is used instead. (For example, as I'm behind one of this proxies, when I visit places like www.whatsmyip.com
, the ip returned is my proxy's, not mine. Another example - when I use the NATcheck on btfaq.com (http://btfaq.com/natcheck.pl
), I always fail the test.)
Wrongly(?) configured trackers would be unable to detect the actual IP address of the user, and thus the user does not get remote connections. For these trackers, I found that manually inputting my IP fixes the problem. (Though your mileage may vary. I can't seem to fix this torrent on this PHPBT tracker.)
I'll try to download from another PHPBT tracker and see if I get the same results.