NIC Bind + ipv6 enabled causes qbittorrent to only listen on ipv6.

[xinot89]

qBittorrent version and Operating System

Qbittorrent 4.0.3, Windows server 2012 R2

What is the problem

Qbittorrent won't listen on ipv4 port when NIC bind and IPV6 are enabled.

What is the expected behavior

Qbittorrent listening ipv4+ipv6 at same time with NIC bind enabled.

Steps to reproduce

On machine with several network interfaces, bind to one + enable ipv6.

Extra info(if any)

No bind & ipv6 unticked qbittorrent still listens on both stacks, same thing with ipv6 ticked without NIC binding.
With NIC bind with ipv6 unticked there's no listening ipv6 ports on binded or any other NICs.
With both, NIC bind + ipv6 ticked qbittorrent only listens to that bound NIC's IPV6 address.
If i disable ipv6, qbittorrent listens to bound IPV4 interface normally.

Listening interfaces / ip versions checked from windows' resource manager.

[xinot89]

...Specific ip address to bind -field is also set "All addresses"

If i select ipv6 address to this field, everything continues same way, as with "All addresses"
If i select ipv4 address to this field, qbittorrent stops listening ipv6 and starts listening ipv4 loopback interface. (my bad, had ipv6 ticked with ipv4 address bound so that's not so relevant bug, without ipv6 ticked listens as expected at specified ip)

[senposage]

related ?
#8258

[DefiantPenguin]

IPv6 issue with SOCKS5 as well. When Ipv6 option is selected and proxy you're using doesn't support IPv6 no fallback to IPv4; what makes worse is that this is intermittent.

I didn't bind to a specific interface or address

[xinot89]

Managed to reproduce original problems with qBittorrent 4.0.3 on Windows 10 pro x64 (Clean install):

Without bind, ipv6 tick box doesn't do anything to listening ports, qBittorrent by default listens to v4&v6. With bind you can choose with tick box whether to listen v4 or v6 but not both simultaneously under any circumstances.

[e00E]

I can confirm this bug on Linux. I have both ipv4 and ipv6. As pointed out already when using Any Interface and not ticking Listen on IPv6 address qbittorrent binds to both ipv4 and ipv6. This is expected according to the libtorrent setting listen_interfaces.
When selecting a specific interface and not ticking the box only ipv4 is bound and when ticking the box only ipv6 is bound.
This is not in accord with the qbittorrent documentation https://github.com/qbittorrent/qBittorrent/wiki/Explanation-of-Options-in-qBittorrent#Advanced :

allows qBittorrent to listen on IPv6 address in addition to the old, standard IPv4.

[Ovsyanka]

Any news about this issue? I faced with the same situation on linux @e00E described.

[sledgehammer999]

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.