UPnP configuration no longer working

Bug #1644512 reported by Brett Dunbar
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
DC++
Confirmed
High
Unassigned

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.

Revision history for this message
eMTee (realprogger) wrote :

Please make sure it's not a firewall issue, follow http://dcplusplus.sourceforge.net/webhelp/faq_unblock.html

Revision history for this message
Brett Dunbar (bpd) wrote :

That is the first thing I considered, that there might be some problem with the firewall rules. So I tried turning the windows firewall off entirely so it couldn't be blocking DC++; it made no difference.

All I have done is change the version of DC++ I use. The problem is definitely with DC++. 0.851 can communicate with the uPnP on my router 0.863 can not. Whatever the problem is it was introduced with version 0.860.

Revision history for this message
eMTee (realprogger) wrote :

Thank you for your report Brett, we've just wanted to rule out the most common problem causing this.
Indeed, we upgraded the MiniUPnP library and made some refactoring in the port mapper area in 0.860.
I guess it's time to improve the error reporting of the Mapper class. IIRC currently it reports the above error string in case of any problems, including when no UPnP capable devices found and that is quite misleading.

Revision history for this message
Brett Dunbar (bpd) wrote :

With 0.865 the error message is better. It states the problem more clearly. However the substantive problem is still there. For whatever reason the changes introduced with 0.860 broke the MiniUPnP with my device. So I have gone back to 0.851 which is able to communicate with the uPnP. This version of the MiniUPnP library doesn't work with some equipment that the old version did work with. Given that the hardware I am using is that supplied by BT infinity this is going to be affecting quite a lot of people with fast internet (fibre to the cabinet) in the UK.

Revision history for this message
eMTee (realprogger) wrote :

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
importance: Undecided → High
Revision history for this message
eMTee (realprogger) wrote :

And we already removed 0.851 from the user accessible downloads. That was a mistake.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.