Topics created by novac1

When I've been in China I had to:

disable the DHT and local peer discovery in order to avoid getting probed by the GFW disable uTP and restort to the traditional TCP-based transport

In the past, people rewrote the window size (by interception) to a smaller, randomly chosen value.
The GFW regexp(s) did not recognize the torrent traffic.
But now the fw seems to do stream reassembly, so this is not effective.

I asked some friends in China…
It doesn't seem gaytorrent is actually the subject of dns poisoning, nor ip blocking.
But the topology of the GFW is not homogenous, so it's difficult to be really sure.

If this is the case you may try to tunnel the connection to the tracker. (shadowsock, psiphon, tor, lantern, streisand, ...)
In my case, a VPN wasn't an option.. The connection for high-bandwith streams isn't stable in mainland since VPNs are banned.

Again, we need to know the tracker status message, as there are any number of things that can cause the status to say "Not Working". At the moment, there are no issues with the tracker, however some users in some parts of the world do have issues either with their government, or their ISP not cooperating with our server hosting provider, particularly with the tracker. In some cases, this is DNS related, and in other cases, the problem is routing based. In most cases, the use of a VPN such as PrivateVPN will help to get around this issue. Just make sure that you are using a server that forwards ALL ports, or that your torrent client is using the port that the VPN is forwarding.