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

DHT does not working via vpn #22062

Open
RazerStvH opened this issue Dec 25, 2024 · 2 comments
Open

DHT does not working via vpn #22062

RazerStvH opened this issue Dec 25, 2024 · 2 comments

Comments

@RazerStvH
Copy link

qBittorrent & operating system versions

qbittorrent v5.0.2
libtorrent 0.14.0-1
libtorrent-rasterbar 1:2.0.10-3
OS Arch linux

What is the problem?

I apologize in advance for the machine translation, I do not fully speak English.

The problem is that I can't connect to DHT via VPN. I use VLESS+REALITY via NekoBox. TUN mode. <

The download only takes place if there is a tracker. It is impossible to download anything using a magnet link without a tracker. At the same time, recoil occurs, but very slowly.

Qbittorrent writes that there are no direct connections and the number of DTH nodes is 0

The network interface was exposed on neko-tun.

I say right away, UDP works through this VPN. I can use discord, mumble, and other applications that require UDP. The iperf test also shows a successful connection. So I guess the problem is with qbittorrent. It is also worth noting that disabling upnp on the router and the closed port do not affect the operation. Unless the recoil rate drops. But at the same time, the client continues to show the DHT and the presence of a direct connection.

Steps to reproduce

  1. Turned on nekobox in tun mode
  2. Enabled the network interface in neko-tun
  3. Restarted qbittorrent
  4. I see no connections

Additional context

изображение
изображение
изображение
изображение

Log(s) & preferences file(s)

execution log

25.12.2024 21:18 - Power management found suitable D-Bus interface. Interface: org.gnome.SessionManager
25.12.2024 21:18 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Sun Dec 1 05:19:17 2024.
25.12.2024 21:18 - Successfully listening on IP. IP: "fe80::d570:e3bf:bde0:975%neko-tun". Port: "UTP/43093"
25.12.2024 21:18 - Successfully listening on IP. IP: "fe80::d570:e3bf:bde0:975%neko-tun". Port: "TCP/43093"
25.12.2024 21:18 - Successfully listening on IP. IP: "172.19.0.1". Port: "UTP/43093"
25.12.2024 21:18 - Successfully listening on IP. IP: "172.19.0.1". Port: "TCP/43093"
25.12.2024 21:18 - UPnP/NAT-PMP support: ON
25.12.2024 21:18 - Embedded Tracker: Now listening on IP: 0.0.0.0, port: 9000
25.12.2024 21:18 - Encryption support: ON
25.12.2024 21:18 - Anonymous mode: OFF
25.12.2024 21:18 - Peer Exchange (PeX) support: ON
25.12.2024 21:18 - Local Peer Discovery support: ON
25.12.2024 21:18 - Distributed Hash Table (DHT) support: ON
25.12.2024 21:18 - HTTP User-Agent: "qBittorrent/5.0.2"
25.12.2024 21:18 - Peer ID: "-qB5020-"
25.12.2024 21:18 - Trying to listen on the following list of IP addresses: "neko-tun:43093"
25.12.2024 21:18 - Using config directory: /home/user/.config/qBittorrent
25.12.2024 21:18 - qBittorrent v5.0.2 started. Process ID: 21905
@HanabishiRecca
Copy link
Contributor

You probably want to monitor network activity on the client start. Capture neko-tun interface via Wireshark to see what's happening.

@RazerStvH
Copy link
Author

I also noticed that the client is after importing the files .torrent, which had previously been distributed normally, stopped seeing peers and seeds. It also loads the processor at 100%, although nothing happens. There is no distribution or content verification.

HanabishiRecca, Biglist is working fine. He sees the dht and returns the data normally. But I don't like its overloaded interface, as well as the stability of its operation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants