linuxdcpp-team team mailing list archive

[poy <1269933@xxxxxxxxxxxxxxxxxx>]

i would like the setting mentioned in comment #1.

connectivity retries i am more dubious of, however; eMTee has explained
the reasons. this will require extensive real-world testing if we really
want to have it in.

specific point about the patch: don't set autoDetected = false after
passive mode has been "auto-detected". the autoDetected variable is not
meant to signify active mode success but only that auto-detection has
ended. it has other uses, for ex in the status message obtained with
"/conn". either add another flag for active mode success or just use
autoSettings[SettingsManager::INCOMING_CONNECTIONS].

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

Title:
  Request: Additional timer for creating port mappings

Status in AirDC++:
  New
Status in DC++:
  New

Bug description:
  There are more and more passive users around. Many of these users use
  the settings for automatically create the port mappings at startup. It
  happens, more often nowadays, that the mappings fail due to whatever
  reasons without any changes to the client/router. Users often fix this
  by restarting either client/computer/router. What if there was a timer
  (in addition to the port mapping) that would enable the client to
  retry the mapping every X s/m/h  or something?

  Version: AirDC++ 2.70a-123-g8b45f-d

  Br Charlie

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