Which is strange. I've been running ktorrent on the same machine with the same ports "allocated" to ktorrent for some time now, and its recently just started popping up that error. It seems to think that all 9 ports starting with 25000 are in use, when infact they are not.

Now, I got the error to go away by setting it to only listen on a single interface instead of "All Interfaces". Still it seems like a strange issue.

Tomasu wrote:Which is strange. I've been running ktorrent on the same machine with the same ports "allocated" to ktorrent for some time now, and its recently just started popping up that error. It seems to think that all 9 ports starting with 25000 are in use, when infact they are not.

Now, I got the error to go away by setting it to only listen on a single interface instead of "All Interfaces". Still it seems like a strange issue.

Is IPv6 disabled ?

George wrote:

Tomasu wrote:Which is strange. I've been running ktorrent on the same machine with the same ports "allocated" to ktorrent for some time now, and its recently just started popping up that error. It seems to think that all 9 ports starting with 25000 are in use, when infact they are not.

Now, I got the error to go away by setting it to only listen on a single interface instead of "All Interfaces". Still it seems like a strange issue.

Is IPv6 disabled ?

Yup, having IPv6 enabled on my network really messes things up when sites decide to add IPv6 AAAAs to their DNS. For a while I started loosing site after site till I realized they were all responding with ipv6 addresses instead of ipv4. (and my isp hasn't moved to ipv6 yet, or even a technology that supports ipv6. docsis 1.1 blows. but they are finally working on the transition to docsis3 no idea when that'll happen, or if they'll bother telling me so I can get a new modem)

svn up, it should be fixed with current SVN, if binding fails on the IPv6 address :: (all interfaces in IPv6), KT will then try the IPv4 address 0.0.0.0

George wrote:svn up, it should be fixed with current SVN, if binding fails on the IPv6 address :: (all interfaces in IPv6), KT will then try the IPv4 address 0.0.0.0

Seems to work.