Binding AirDC++ to a virtual interface isn't possible. Only "Any (0.0.0.0)" and "Ethernet (x.x.x.x)" are shown, despite there being 2 more virtual interfaces from a privacy VPN . The 2 available interfaces are using Wintun and TAP-Windows Adapter V9 respectively.
Other software, qBittorrent for example, can see the interface(s) and can successfully bind to that interface.
Expected behavior
All (connected) network adapters/interfaces, virtual or physical, should be listed and selectable. If the interface isn't ready, AirDC++ should not fall back on a different interface.
Prerequisites
Describe the issue
Binding AirDC++ to a virtual interface isn't possible. Only "Any (0.0.0.0)" and "Ethernet (x.x.x.x)" are shown, despite there being 2 more virtual interfaces from a privacy VPN . The 2 available interfaces are using Wintun and TAP-Windows Adapter V9 respectively.
Other software, qBittorrent for example, can see the interface(s) and can successfully bind to that interface.
Expected behavior
All (connected) network adapters/interfaces, virtual or physical, should be listed and selectable. If the interface isn't ready, AirDC++ should not fall back on a different interface.
Actual behavior
Only physical adapters are shown.
Steps to reproduce the behavior if needed
Screenshot
No response
Crash log
No response
AirDC++ version and architecture (x86 or x64)
4.11 and 4.21 x64
Operating System name, version and architecture
Windows 10 pro and Windows 11 pro x64
Additional information
VM and physical machine show the same behaviour.