We want to fix this somehow by adding a possibility to detect these slightly ill behaving routers so this remains open. Especially after seeing your link suggesting there's a whole lot of newish TP-Link models suffer from this issue.
The Windows UPnP mapper implementation was great option when it's been added ~20 years ago but it was pretty unstable and error prone, not working well with many router models and produce false positives (report success when port mapping won't work) with others. Eventually we thought MiniUPnP would cover it all as we've found great rate of successful port mappings with it. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/1993817 Title: Unable to create port mappings in DC++ with MiniUPnP mapper while other apps using MiniUPnP succeed Status in DC++: Confirmed Bug description: Tested DC++ up to version 0.880. Windows 10 x64. System Log: [17:35] Port mapping: Failed to initialize the MiniUPnP interface [17:35] Port mapping: Failed to map the Transfer port (54648 TCP) with the NAT-PMP interface [17:35] Port mapping: Failed to create port mappings I tried to select a specific network interface in the settings, disable all network interfaces except one. At the same time ApexDC++ and qBittorrent are successfully opened ports with UPnP. To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/1993817/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
