This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Can't download anything with ktorrent 2.1/2.2

Tags: None
(comma "," separated)
Warp
Registered Member
Posts
16
Karma
0

Sun Jul 15, 2007 9:26 am
As I have mentioned, I have no problems with ktorrent 1.2 nor with BitTornado. They download that file and all other files just fine. So it can't be a question of firewall settings.

As for ktorrent 2.2 settings, I use the defaults. What else can I do?
MoDaX
Registered Member
Posts
241
Karma
0
OS

Sun Jul 15, 2007 9:39 am
Warp wrote:As for ktorrent 2.2 settings, I use the defaults. What else can I do?


Port/UDP tracker port/DHT port must be open/forwarded to your PC. Fire up wireshark and see what's going on your KTorrent ports under the hood.
caf4926
Registered Member
Posts
14
Karma
0

Mon Jul 16, 2007 2:44 pm
I'm jumping in on this thread because I just re-installed suse 10.2 and picked up ktorrent beta from guru and noticed it was working fine without opening ports in the suse firewall. I thought this was strange. I would expect to have to do this. I installed Azureus too and it said it needed the port opening, so I had to add one for it. But your opening comment WARP, suggests ktorrent doesn't need this?

Is this right, and if so, how is it achieved?
lucke
Registered Member
Posts
205
Karma
0

Mon Jul 16, 2007 2:49 pm
BitTorrent clients will (should) work without forwarding/opening ports, although not as effectively.
stevenofnine
Registered Member
Posts
62
Karma
0

Mon Jul 16, 2007 7:16 pm
He's right. The simple explanation is this:

With a port open, YOU can be asked for data by anyone.

With no port open, you can not be asked for data by others without a port open.

So, the data in the swarm all has to go through the users with open ports.

Azureus tells you you have a problem. KTorrent doesn't.

Mebbe, as Linux users we're expected to know better... :D
lucke
Registered Member
Posts
205
Karma
0

Mon Jul 16, 2007 7:23 pm
Since 2.2 KTorrent tells you when there are no incoming connections (main (not DHT) port isn't open/forwarded).
Warp
Registered Member
Posts
16
Karma
0

Tue Jul 17, 2007 12:34 pm
MoDaX wrote:Port/UDP tracker port/DHT port must be open/forwarded to your PC. Fire up wireshark and see what's going on your KTorrent ports under the hood.


With that, do you mean that ktorrent 2.2 behaves *differently* from ktorrent 1.2 and that, unlike the latter, 2.2 expressly requires the ports to be open/forwarded or else it will just not work? I don't understand why 2.2 would have been changed that way. It makes it useless if, for example, you *can't* open/forward those ports.

I can open the ports used by ktorrent 2.2 in the Suse firewall. However, I'm not completely sure what you mean by forwarding. If by that you mean that my ISP must forward some ports of some server of theirs to my computer, I think that's a no-can-do.

Moreover, as I have wrote earlier, I *did* try opening the ports used by ktorrent 2.2 in the Suse firewall. It didn't make any difference.

Currently I'm stuck with ktorrent 1.2. I would really like to use 2.2 because it has more advanced features (for example, if I start downloading a file I already have, it starts seeding it automatically, unlike 1.2 which does something odd).

And besides, if it was just a question of ktorrent not getting any connections, shouldn't it report the download to be "stalled", not "downloading" as it does (even though it doesn't download a single byte)? It also reports a download rate of over 0 even though it's not downloading anything. That's what's odd about it. I think this should be a relevant issue here.
George
Moderator
Posts
5421
Karma
1

Tue Jul 17, 2007 7:31 pm
Warp wrote:
MoDaX wrote:Port/UDP tracker port/DHT port must be open/forwarded to your PC. Fire up wireshark and see what's going on your KTorrent ports under the hood.


With that, do you mean that ktorrent 2.2 behaves *differently* from ktorrent 1.2 and that, unlike the latter, 2.2 expressly requires the ports to be open/forwarded or else it will just not work? I don't understand why 2.2 would have been changed that way. It makes it useless if, for example, you *can't* open/forward those ports.


If the port is not opened and forwarded (if you are behind a router), you will not get incoming connections. KT will still work, as long as it can connect to peers.

I can open the ports used by ktorrent 2.2 in the Suse firewall. However, I'm not completely sure what you mean by forwarding. If by that you mean that my ISP must forward some ports of some server of theirs to my computer, I think that's a no-can-do.


If you don't have a router, you don't need port forwarding.

And besides, if it was just a question of ktorrent not getting any connections, shouldn't it report the download to be "stalled", not "downloading" as it does (even though it doesn't download a single byte)? It also reports a download rate of over 0 even though it's not downloading anything. That's what's odd about it. I think this should be a relevant issue here.


So you are downloading something. Can you post the log file ? You can find it in ~/.kde/share/apps/ktorrent/log
Warp
Registered Member
Posts
16
Karma
0

Wed Jul 18, 2007 10:23 pm
Can you post the log file ? You can find it in ~/.kde/share/apps/ktorrent/log


Thu Jul 19 01:04:05 2007: Bound to port 6881
Thu Jul 19 01:04:05 2007: File limit allready at maximum
Thu Jul 19 01:04:05 2007: Data limit allready at maximum
Thu Jul 19 01:04:05 2007: Loading file /tmp/yoshisisland-tas-deign,laughinggas.avi-4.torrent
Thu Jul 19 01:04:05 2007: Encoding : UTF-8
Thu Jul 19 01:04:05 2007: OutputPath =
Thu Jul 19 01:04:17 2007: Moving data for torrent yoshisisland-tas-deign,laughinggas.avi to /home/warp/
Thu Jul 19 01:04:17 2007: Data directory changed for torrent 'yoshisisland-tas-deign,laughinggas.avi' to: /home/warp/
Thu Jul 19 01:04:17 2007: Starting download
Thu Jul 19 01:04:17 2007: Pre-allocating diskspace
Thu Jul 19 01:04:17 2007: Preallocating file /home/warp/.kde/share/apps/ktorrent/tor0/cache (28046444 bytes)
Thu Jul 19 01:04:17 2007: file_size = 28046444
Thu Jul 19 01:04:17 2007: PreallocationThread has finished
Thu Jul 19 01:04:17 2007: Selected tracker http://bisqwit.iki.fi:6969/announce (tier = 1)
Thu Jul 19 01:04:17 2007: Switching to tracker http://bisqwit.iki.fi:6969/announce
Thu Jul 19 01:04:17 2007: Doing tracker request to url : http://bisqwit.iki.fi:6969/announce?pee ... 4%e2%e1%92
Thu Jul 19 01:04:17 2007: Doing scrape request to url : http://bisqwit.iki.fi:6969/scrape?info_ ... 4%e2%e1%92
Thu Jul 19 01:04:18 2007: Scrape : leechers = 3, seeders = 43
Thu Jul 19 01:04:18 2007: IP 0.0.0.0 banned.
Thu Jul 19 01:04:18 2007: Initiating connection to <an ip address>
(lots of similar lines)
Thu Jul 19 01:04:18 2007: Authentication to <an ip address> : ok
Thu Jul 19 01:04:18 2007: Starting socketmonitor threads
Thu Jul 19 01:04:18 2007: Authentication to <an ip address> : ok
(lots of similar lines)
Thu Jul 19 01:04:19 2007: Connection closed
Thu Jul 19 01:04:38 2007: Timeout occurred
Thu Jul 19 01:04:38 2007: Authentication to <an ip address> : failure
Thu Jul 19 01:04:38 2007: Timeout occurred
Thu Jul 19 01:04:38 2007: Authentication to <an ip address> : failure
Thu Jul 19 01:05:59 2007: Doing tracker request to url : http://bisqwit.iki.fi:6969/announce?pee ... 4%e2%e1%92
Thu Jul 19 01:05:59 2007: Saving 1 chunk downloads
Thu Jul 19 01:05:59 2007: Saving list of peers to /home/warp/.kde/share/apps/ktorrent/tor0/peer_list
Thu Jul 19 01:05:59 2007: Stopping socketmonitor threads
Thu Jul 19 01:05:59 2007: Starting download
Thu Jul 19 01:05:59 2007: Loading list of peers from /home/warp/.kde/share/apps/ktorrent/tor0/peer_list (num_peers = 13)
Thu Jul 19 01:05:59 2007: Loading 1 active chunk downloads
Thu Jul 19 01:05:59 2007: Loading chunk 426
Thu Jul 19 01:05:59 2007: Announce ongoing, queueing announce
Thu Jul 19 01:05:59 2007: Doing tracker request to url : http://bisqwit.iki.fi:6969/announce?pee ... 4%e2%e1%92
Thu Jul 19 01:05:59 2007: Saving 1 chunk downloads
Thu Jul 19 01:05:59 2007: Saving list of peers to /home/warp/.kde/share/apps/ktorrent/tor0/peer_list
Thu Jul 19 01:05:59 2007: SynchronousWait
George
Moderator
Posts
5421
Karma
1

Fri Jul 20, 2007 6:47 pm
What happens if you change the port ?
Warp
Registered Member
Posts
16
Karma
0

Fri Jul 20, 2007 9:49 pm
I tried changing the port to 10001 and the UDP port to 10002. I even tried opening those two ports in the Suse firewall. It didn't make any difference.
George
Moderator
Posts
5421
Karma
1

Sat Jul 21, 2007 11:33 am
You need to restart KT before the changes will take affect.

If that doesn't work, enable encryption.
Warp
Registered Member
Posts
16
Karma
0

Sat Jul 21, 2007 9:39 pm
I upgraded my system to Suse 10.2 (I have been planning to do this for a long time) and I'm now using the ktorrent 2.x which came with that. So far it seems to work ok.
Jargon
Registered Member
Posts
2
Karma
0

am i downloading right?

Tue Jul 31, 2007 2:42 am
hey everyone, im quite new to kubuntu and like all others i need help. i went and downloaded a movie file and when i tried to watch it,... it was exe (if that helps at all) and it wont let me watch it or anything. did i download it right? cause i noticed that at the bottom of my ktorrent window it says no incoming connections. how do i change my firewall or make it work? if i did it right then what do i have to do to watch it?
MoDaX
Registered Member
Posts
241
Karma
0
OS

Re: am i downloading right?

Tue Jul 31, 2007 9:38 am
Jargon wrote:hey everyone, im quite new to kubuntu and like all others i need help. i went and downloaded a movie file and when i tried to watch it,... it was exe (if that helps at all) and it wont let me watch it or anything. did i download it right?

No, you've downloaded a fake. Movie never come in the form of .exe. Video files end with .avi, .mov, .wmv, high-definition ones are usually .mkv, a bunch of rars is also possible (you need to extract them before watching). Use media player like kaffeine, mplayer etc. to watch video files


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]