linuxdcpp-team team mailing list archive

[eMTee <1269933@xxxxxxxxxxxxxxxxxx>]

I think it would be better to decide first that if there's anything to
fix here at all.

First of all I'd beg to differ to the reporter as since the Automatic
Connectivity Setup introduced the amount of passive users in DC network
(and along with it, the support requests about connection problems) has
been definitely lowered.

Secondly, I fail to see how periodic port mapping re-attempts would
result much more active users. If the port mapping fails for the first
try it's unlikely it'll succeed for any subsequent tries.

Moreover if the search/download doesn't work, the user won't wait for
30/60/whatever minutes, rather they'll do some action a lot sooner
which, in almost all cases, includes a client restart. If the user
restarts the client/OS then the required redetect will happen at the
next start.

And at last but not least, while the case in comment #1 is not related
to this report (it's more likely because of a delayed $UserIP procesing
due to the excessive resource demand of auto-connecting to extremly
large amount of hubs - and the problem goes away automatically after the
sent IP is processed), timely redoing the connection detection possibly
results just that exact confusing error message in some hub/script usage
scenarios.

So I guess it needs some more thinking of what we can gain and what to
lose with this new feature.

-- 
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