Comment 1 for bug 1269933
Revision history for this message
| LoRenZo (lorenzo-mailbox-deactivatedaccount) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I believe this is sort of related to what I wanted to request.
I am getting the following every once in a while for a couple of hubs:
[17:54] <BOT> Your search IP is not <INTERNAL IP> but <EXTERNAL IP>.
[17:54] *** Connection closed
Reconnecting to the specific hub right away solves the issue from what I can tell.
I believe that being automatically connected to numerous hubs when the client starts up might be responsible for this.
I was thinking of having a small delay between the port mappings and the automatically initiated connections towards the favorite/saved state hubs.
I am using the lastest available revision of DC++ 0.831, but I saw this in case of older revisions of the same client as well.