[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 141483] ktorrent uses 95% of the CPU
From:       Jakub Suder <jakub.suder () gmail ! com>
Date:       2007-03-21 20:08:11
Message-ID: 20070321200811.28237.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=141483         




------- Additional Comments From jakub.suder gmail com  2007-03-21 21:08 -------
Only if those pings had the outside address of the router ($INET_ADDRESS = \
213.134.183.78) set as destination, I think - and they shouldn't, as there's no \
bittorrent client on the router - they should be addressed to some peer's IP, am I \
right? Unless ktorrent really intends to ping the router for some reason...

That's theory, and in practice I can see a few peers with IP 213.134.183.78 (4 out of \
22 total at the moment) in the list in the "peers" tab (the one with flags), I don't \
know why. So that could be the problem - peers with my IP get somehow on the list, \
ktorrent tries to ping them and the router sends the pings back to me...

Wait - is it possible, as ktorrent doesn't know now it's really running on \
213.134.183.78, and thinks it runs only on 10.1.1.21, that it sometimes finds the \
outside address through the search procedure which it uses to find other peers, finds \
that this peer (which is itself) has a part of the file downloaded (of course it \
does), and tries to connect to it? So to solve this, ktorrent should either \
automatically find if it's behind a NAT and what it's external IP is (if it's \
possible), and don't try to connect to that IP, or allow the user to enter the IP \
manually... am I thinking correctly?


[prev in list] [next in list] [prev in thread] [next in thread]