I can’t tell what you meant either. Your communication is very unclear.
I’m guessing that you want to know why you aren’t getting any DHT connections. Is that correct?
If so, the issue is probably that you have your listen port blocked for the UDP protocol, which is what DHT uses exclusively. In order for DHT to work, you need to unblock your listen port on all of your active firewalls for both TCP and UDP protocols.
For some firmware firewalls, you are forced to choose one or the other, so this has to be done with two separate rules, one allowing each.
For most others, you can specify “Both”, or “Either” or “All” protocols, which is the same thing.
This might not be the only factor, but it certainly needs to be checked and resolved before proceeding.
You do not need to have DHT available in order to use bittorrent or Bitcomet.
That is correct. The choice to support DHT and PEX is made by the creator of the torrent, at the time of creation, and it can’t be overruled by anyone including him: if he wants to change this he must create a different torrent.
No one is required to use DHT – it can be disabled by the client for all torrents or for a particular torrent, or its underlying protocol can be blocked.
Some sites such as ThePirateBay no longer support their own tracker at all, and require the use of DHT and PEX for peerfinding, so disabling DHT altogether largely means you cannot use those sites.
