Uncia on 6/11/2006 at 20:15
Then I must be special, because my event log was filled with "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". *waits for his short bus*
dj_ivocha on 6/11/2006 at 22:41
Quote Posted by Uncia
number of
concurrent TCP connect
attemptsThat's what I meant - by default you can't try to connect to more than 10 different addresses at once. :)
But as soon as one of those 10 attempts is through (by either the remote client accepting or refusing the connection, or not responding at all in the allocated time frame), you are again allowed to try another connection. Usually each attempt takes just a couple of seconds to complete, so you have a continuous rotation until you've connected to or tried to connect to all the peers in the swarm.
Most (all?) bit torrent clients have a built-in limiter, that is usually configured to only allow the client 10 or less simultaneous connection attempts. If your log is filled with warnings, then your client is just not configured properly and each of its attempts to connect after the 10th get blocked. That shouldn't be a problem, as it will just try again as soon as the half-open connections drop to 9 or less again, unless it doesn't know the previous attempts were rejected, and thought the remote peers simply didn't answer, thus flagging them as non connectible and not trying again. But I doubt that's the case.
Or do you always get only 10 connected peers, even though a torrent has many more?
Uncia on 6/11/2006 at 23:58
Probably more, but since I had nothing to lose by upping the restriction to 50 I did anyway (and thus cannot check now). It might not make a difference in the long run, but hey, I enjoy an error-free log. :)
Shockedder on 7/11/2006 at 00:41
Linux me little babies .... :p
Last time I checked about 160 open tcp connections on the torrents...
That is with bittorrent .
:weird:
