qbittorrent will not feedback the proxy IP to the tracker when the proxy is enabled

[wenwenwenzq]

qBittorrent & operating system versions

qBittorrent: v4.6.4
Operating system: Windows11 23H2/22631.3527
Qt: 6.4.3
Libtorrent: 1.2.19.0
Boost: 1.84.0
OpenSSL: 1.1.1w
zlib: 1.3.1

What is the problem?

qbittorrent will not feedback the proxy IP to the tracker when the proxy is enabled,This will cause the IP returned by the client to the tracker to be the local IP instead of the proxy IP.

In addition, it will also cause some special methods to fail, such as using frp+socks5 to achieve the local machine to obtain the public network IP and open the port. Then external intranet users access the proxy IP, and frp returns the data to the local intranet, thus Realize intranet penetration + data backhaul, allowing the client to monitor external intranet users and transfer data to each other through proxy IP.

I have tested the old software BitSpirit in 2010, the modern BitComet and µTorrent. These softwares will actively feedback the proxy IP to the tracker so that the intranet client through the proxy can normally obtain users and return data, but I found that in When the proxy is enabled, qibittorrent will not feedback the proxy IP to the tracker, causing other users to be unable to find the proxy IP when downloading, because qibittorrent feedback to the tracker is the local IP, and the local IP is in the internal network and cannot monitor the external network. Intranet users.

Steps to reproduce

Configuration like the picture, I use xxx because I don’t want to reveal my proxy IP address for privacy

Additional context

none

Log(s) & preferences file(s)

no logs

[glassez]

no logs

👎

[wenwenwenzq]

I used Google Translate, which may not be accurate.

The overall meaning is that qbittorrent will not feedback the proxy IP to the tracker, but will feedback the internal network IP, that is, the users under the public network NAT. The software 14 years ago has already thought of this operation, but the modern qbittorrent has not thought of feedback to the proxy. The IP is given to the tracker, but the internal IP of the user under the public network NAT is returned as is, which is confusing.