DHT does not work via vpn #16487

New issue

Open

opened 2026-02-22 03:09:34 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 03:09:34 -05:00

Owner

Originally created by @RazerStvH on GitHub (Dec 25, 2024).

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

Turned on nekobox in tun mode
Enabled the network interface in neko-tun
Restarted qbittorrent
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

Originally created by @RazerStvH on GitHub (Dec 25, 2024). ### 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 ![изображение](https://github.com/user-attachments/assets/81ea5839-cc75-44a3-b0c6-01102b7854fe) ![изображение](https://github.com/user-attachments/assets/05af3b63-5860-4e26-bfd7-c7ce886d8b67) ![изображение](https://github.com/user-attachments/assets/b639a099-433d-4338-93fd-51234e3a0ae2) ![изображение](https://github.com/user-attachments/assets/782bcd1b-0f0e-47b6-9d50-1563f38e7666) ### 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 ```

deekerman added the

Proxy/VPN

label

2026-02-22 03:09:34 -05:00

deekerman commented

2026-02-22 03:09:41 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Dec 25, 2024):

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

@HanabishiRecca commented on GitHub (Dec 25, 2024): You probably want to monitor network activity on the client start. Capture `neko-tun` interface via Wireshark to see what's happening.

deekerman commented

2026-02-22 03:09:43 -05:00

Author

Owner

@RazerStvH commented on GitHub (Dec 25, 2024):

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.

@RazerStvH commented on GitHub (Dec 25, 2024): 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](https://github.com/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.