I also still get reports privately about this and as I mentioned before, the
observable stats of active mode clients in the wild went really bad with
version 0.86x.
Something's clearly broken with MiniUPnP 3 and numerous gateways /
configurations.
Above the improved error reporting I suggest re-adding the OLD_MINIUPNPC define
facility, support the old interface which would provide possibility to give
builds with the previous MiniUPnP to the reporting people, so comparing the
improved log messages might shed some light of where's the trouble...
** Changed in: dcplusplus
Status: New => Confirmed
** Changed in: dcplusplus
Importance: Undecided => High
--
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
_______________________________________________
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
