linuxdcpp-team team mailing list archive

[eMTee <1644512@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1993817 ***
    https://bugs.launchpad.net/bugs/1993817

MiniUPnP's detection algrorythm keeps evolving with time and since this report.
With improved error checking it filters out non-standard situations and devices in its discovery. Our mapper don't process these extensive information (keeps using the returned defaults as the best choice - which the library keeps narrowing down in its evolution) leading to problems for some users.

A duplicate of this bug added where there is another example - the
reporter has a device with non-standard responses and thus out of the
default list of discovered devices.

A complete solution would be to list all the discovered devices for the
user when manual connectivity setup has been chosen and let them select
the device they wish to use, at their own risk.

** This bug has been marked a duplicate of bug 1993817
   Unable to create port mappings in DC++ with MiniUPnP mapper while other apps using MiniUPnP succeed

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1644512

Title:
  UPnP configuration no longer working

Status in DC++:
  Confirmed

Bug description:
  I have a BT Homehub 3 with an openreach fibre modem to connect to the
  BT infinity FTTC service. The previous version of DC++ (0.851) could
  talk to the mini MiniUPnP interface and set up an active connection.

  The system log in 0.851 is like this

  [21:23] Connectivity: Determining the best connectivity settings...
  [21:23] Connectivity: Local network with possible NAT detected, trying to map the ports...
  [21:23] Connectivity: Port mapping: Successfully created port mappings (Transfers: 15509, Encrypted transfers: 15510, Search: 51248) on the "WANDevice" device with the MiniUPnP interface
  [21:23] Connectivity: Port mapping: Failed to get external IP
  [21:25] File list <C:\Users\Brett\AppData\Roaming\DC++\files.xml.bz2> generated
  [21:26] Connectivity: Port mapping: Successfully removed port mappings from the "WANDevice" device with the MiniUPnP interface
  [21:26] Connectivity: Determining the best connectivity settings...
  [21:26] Connectivity: Local network with possible NAT detected, trying to map the ports...
  [21:26] Connectivity: Port mapping: Successfully created port mappings (Transfers: 15542, Encrypted transfers: 15543, Search: 50056) on the "WANDevice" device with the MiniUPnP interface
  [21:26] Connectivity: Port mapping: Failed to get external IP

  An active connection is successfully configured.

  The system log in 0.863 is like this

  [10:44] Connectivity (IPv4): Determining the best connectivity settings...
  [10:44] Connectivity (IPv4): Local network with possible NAT detected, trying to map the ports...
  [10:44] Connectivity (IPv6): Determining the best connectivity settings...
  [10:44] Connectivity (IPv6): All IPv6 addresses found are local; disabling connectivity
  [10:44] Connectivity (IPv4): Port mapping: Failed to initialize the MiniUPnP interface
  [10:44] Connectivity (IPv4): Port mapping: Failed to map the Transfer port (19386 TCP) with the NAT-PMP interface
  [10:44] Connectivity (IPv4): Port mapping: Failed to create port mappings
  [10:44] Connectivity (IPv4): Active mode could not be achieved; a manual configuration is recommended for better connectivity
  [10:45] File list <C:\Users\Brett\AppData\Roaming\DC++\files.xml.bz2> generated

  I get only a passive connection.

  I have been reverting to 0.851 due to this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1644512/+subscriptions