linuxdcpp-team team mailing list archive

[eMTee <1629574@xxxxxxxxxxxxxxxxxx>]

See commit [f48813] for a fix. I tested it with a simulating the problem
by breaking my connectivity but one of the reporters will get back to me
later today with the result if it fixes the actual problem.

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

Title:
  Automatic Connectivitiy Setup does not set Passive mode after all
  mapping attempts are unsuccessful (DC++ 0.86x)

Status in DC++:
  Confirmed

Bug description:
  There were a couple of reports with connectivity problems after upgrading 0.851 -> 0.86x like https://answers.launchpad.net/dcplusplus/+question/402406 but it seems both reporters forgot to mention initally that they haven't had active mode at all, not even before the update. This has pointed the focus to possible mapping problems with the new MiniUPnP library, however, it does not seem to be the case.
  As the title says their most probable problem is that instead of setting Passive mode, the auto conn setup leaves their connectivity in an indefinite state after all the port mapping attempts failed.

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