What are you talking about? Ofcourse everyone should worry about backdoors and other vulnerabilities. But I'm sceptical if bitlocker is the right solution.
On a serious note I use a lot of tools to circumvent those vulnerabilities.
What are you talking about? Ofcourse everyone should worry about backdoors and other vulnerabilities. But I'm sceptical if bitlocker is the right solution.
On a serious note I use a lot of tools to circumvent those vulnerabilities.
Its a quote from GOT.
What Is Dead May Never Die
I've nothing against NSA_KEY nor Bitlocker, but anything in context with GAFAM I take it with grain of salt.
Some good news. It appears that the tracker didn't had anyone downloading the torrent while I was seeding it. Because I tried seeding a public torrent, and it worked without any issue (although it still states a warning of "no direct connection").
The executive log might just be handy. I was full of questions what is going without the software telling me what it isn't able to.
I'll keep a look out. I saw a few megabytes of upload on the private tracker. Lol.
I was just reusing the ports I've forwarded for i2p
I won't really trust Bitlocker coming from Microsoft.
where can I find the transmission settings?
It's a home PC with no VPN
How can I resolve that?
On my router config, under port forwarding, I've forwarded a port range of 9000-31000. Now qBittorrent is using 30000.
For testing. I've stopped firewalld too. Still no luck.
I reckon it has something to do with advance tab
Is that qBittorrent? If you meant transmission as in the torrenting software, I've never used it. Before switching to qBit I was using aria2 ๐ .
Btw, thanks to all of you, the problem appears to be resolved. Its a matter of tracker requesting seeds now.