Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qBT announcing port as 1 to DHT even when "anonymous mode" is turned off #14602

Closed
showstoppre opened this issue Mar 24, 2021 · 1 comment
Closed
Labels
Network Issues related to network connectivity Not an issue User error, problem unrelated to qBittorrent, feature already implemented, etc

Comments

@showstoppre
Copy link

Please provide the following information

qBittorrent version and Operating System

(4.3.3) Windows 10 and Ubuntu 18.04

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

qBT is announcing port as 1 to DHT in addition to my actual external port. I can confirm that "anonymous mode" is turned off under Tools>Options>BitTorrent. Problem here is that most clients doesn't allow multiple connections to/from same IP(including qBT) by default. So when a remote client obtains peer list from DHT, it sees two peers for same ip (one with correct external port and other with port as '1'). Now there is only a 50% chance that it connects to my client correctly.

I tested using qBT as remote client. My observation is as below. qBT always tries connecting using uTP first then using TCP. It tries one peer for uTP and other for TCP and the first peer to connect is chosen randomly.

Situation #1 - Desired

  • Remote qBT tries connection to my_ip:my_port using uTP. Connection is successful.

Situation #2 - Undesired

  • Remote qBT tries connection to my_ip:1 using uTP. Connection fails.
  • Remote qBT tries connection to my_ip:my_port using TCP. Connection fails as I'm behind CGN

What is the expected behavior

Only my actual external port should be announced to DHT.

Steps to reproduce

Can be observed using any torrents with DHT enabled in settings.

Extra info(if any)

@thalieht thalieht added the Network Issues related to network connectivity label Mar 24, 2021
@showstoppre
Copy link
Author

Closing issue.

Upon more investigation, I identified that the issue is caused by some bad nodes, capturing port as '1', when 'implied_port' argument is set.

@FranciscoPombal FranciscoPombal added the Not an issue User error, problem unrelated to qBittorrent, feature already implemented, etc label Oct 14, 2021
@qbittorrent qbittorrent locked as resolved and limited conversation to collaborators Oct 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Network Issues related to network connectivity Not an issue User error, problem unrelated to qBittorrent, feature already implemented, etc
Projects
None yet
Development

No branches or pull requests

3 participants