I'm running a tracker on my local network and want to use ktorrent to seed files for download over the internet. I have a router connected to a cable modem with a static IP and I use maketorrent to create the .torrents. I have TCP ports 6881-6999 on the router forwarded to the machine running the tracker, and the tracker is visible over the internet.

Here are the steps I've taken. Create .torrent:

Code: Select all

maketorrent-console http://<static ip>:6969/announce <dir>

Open ktorrent and set 'Custom IP' to <static ip>. Open .torrent and choose to download to the parent directory of <dir>. My understanding is that ktorrent should recognize that <dir> already exists and begin seeding. Tracker status is listed as 'OK', but download status is 'Stalled'. The ktorrent log looks like this:

Code: Select all

Doing tracker request to url: http://<static ip>:6969/announce?...
Connecting to peers (1)
IP 0.0.0.0 banned.
Initiating connection to <static ip>
Lets not connect to our self
Authentication(S) to <router ip> : failure
Socket error : remote host closed connection
Authentication to <static ip> : failure

Can anyone explain where I'm going wrong? I'm using KTorrent 1.2 and KDE 3.5.2 on Gentoo.

KTorrent v1.2 won't recognize your download and start seeding the way you described. You should use partfileimport plugin and import your download with it. Then it will be seeded without problems.

OK, after going through the import process the download status is "Seeding" and the tracker shows 1 client with the complete file. Good. However, clients cannot download the seeded files and the ktorrent log still shows the following (the connecting to peers message has changed)

Code: Select all

Doing tracker request to url : http://<static ip>:6969/announce?...
Connecting to 1 peers (1)
IP 0.0.0.0 banned.
Initiating connection to <static ip>
Lets not connect to our self
Authentication(S) to <router ip> : failure
Socket error : remote host closed connection
Authentication to <static ip> : failure

Also, the infowidget Status tab shows that the entire file has been download and that no parts of the file are available. Any ideas?

First of all the ports the KT client is using also need to be forwarded. Obviously they need to be different then the ones the tracker is using.

Second :

Open ktorrent and set 'Custom IP' to <static ip>.

This is only for HTTP announces when you are behind a HTTP proxy. Otherwise peers would be trying to connect to your HTTP proxy instead of your machine. So in this case you need to give your actual IP address to the tracker (normally it just gets that from the HTTP connection)

If the torrent has the correct tracker IP address (that of your router, the WAN IP address), then it should work.

I have TCP ports 6881-6999 forwarded to the PC running the tracker and KT, and I have KT 'Custom IP' set to <static ip>. The torrent was created using <static ip> as the tracker address.

To add another wrinkle to the problem, I've noticed the following. If I start the tracker and run bittorrent-curses --ip <static ip> <torrent>, bittorrent-curses shows a status of 'downloading,' but since there's no seed at this point, no data is transferred. If I then run KT and use the import plugin to seed <torrent>, bittorrent-curses begins downloading but it seems to lose it's connection after just a few seconds. The KT log shows

Code: Select all

Loading plugin infowidgetplugin
Loading plugin partfileimportplugin
Showing KT
Multi file torrent
Checked 50 chunks
Checked 100 chunks
Checked 150 chunks
Checked 200 chunks
Checked 250 chunks
Checked 300 chunks
Checked 350 chunks
Multi file torrent
Starting download
Doing tracker request to url : http://<static ip>:6969/announce?...
Connecting to 3 peers (3)
IP 0.0.0.0 banned.
Initiating connection to <static ip>
Initiating connection to <router ip>
Initiating connection to <static ip>
Socket error : connection actively refused
Authentication to <router ip> : failure
Lets not connect to our self
Authentication(S) to <router ip> : failure
Authentication to <static ip> : ok
Socket error : remote host closed connection
Authentication to <static ip> : failure
Connection Closed
Connection Closed

I'm not sure why three peers are shown. In any case, bittorrent-curses begins downloading after "Authentication to <static ip> : ok" but stops after "Connection Closed." Any idea why this happening?

Just to be completely clear, <static ip> is my internet-visible ip address, and <router ip> is the address of my router on the local network, 192.168.15.1.