Yes it is.

Are you sure that the clients can reach each other ?

They are running on the same computer, so I believe they can.

OK, what IP address did you add to the torrent ?

Also, why are you going to this trouble, when you can just point both clients to the same data and do a data scan ?

I'm trying on the same computer because I only have one computer. My goal is to be able to do this between distant computers, and when it works I will have to try that configuration too.

I added the IP "127.0.0.1" with the port I use for the DHT, and "127.0.0.1" with the port I use for incoming connections too (I'm unsure which one is expected).

I will try stracing the whole thing to see if a connection is attempted.

I just tested "strace -e trace=network ktorrent", and it seems that there is a connection attempt to the client possessing the file, but seems it is UDP it is hard to figure out what goes wrong.

I'm trying to get this going, but cannot set it up properly.
On server with static IP I have ktorrent 3.1.4 and on distant client older for kde 3.5.9.

So on server I created a torrent with IP+6881 dht node - trackerless.
On client I loaded this torrent, but it is not reaching server, even if I manually add peer with server IP on client, I cannot see client IP in ktorrent log on server side, so it is not reaching it.
But if I add client peer on server then immediatelly it starts uploading to client.
Shouldn't it work the other way? Which of ports should I use when creating torrents?

I checked firewalls on both ends and they seems to be set up properly.

kriko wrote:I'm trying to get this going, but cannot set it up properly.
On server with static IP I have ktorrent 3.1.4 and on distant client older for kde 3.5.9.

So on server I created a torrent with IP+6881 dht node - trackerless.
On client I loaded this torrent, but it is not reaching server, even if I manually add peer with server IP on client, I cannot see client IP in ktorrent log on server side, so it is not reaching it.
But if I add client peer on server then immediatelly it starts uploading to client.
Shouldn't it work the other way? Which of ports should I use when creating torrents?

I checked firewalls on both ends and they seems to be set up properly.

I agree it should work the other way around, that when you add the peer on the client that it would start leeching immediately. Port... well, seeing that some network providers are lowering the bandwidth on the normal bittorrent port, you would be best in the free port range, which is 49152-65535.

I already use port 50000+ on both sides, UDP tracker port is set to 4444, DHT to 6881. Maybe it's ktorrent bug - not sure.

In order to seed directly to the other torrent, the other torrent has to be ktorrent as well? that is my question.

pookito wrote:In order to seed directly to the other torrent, the other torrent has to be ktorrent as well? that is my question.

Not really, it just a matter of getting connected, client doesn't really matter.

Ok guys, here is my problem. I have been trying to make this work for the longest time. Since I last posted. And still I can not get ktorrent to work and share files. I give you an example. for the tracker I do the ip address plus the port. Something like this: http://xxx.x.x:444/announce. I try the other torrent client and add my ip address and port. Well, it does not work. After several attempts I noticed on the "trackers tab" a message that says: "Could not connect to host xxx.xxx.x.x: Connection refused." So, Am I supposed to have that problem? Or can I do something else to fix it?

Something else. I noticed that on the first post on this thread it talks about writting the port number in the torrent. What port would that be? because I can see 2 port numbers on network section. The first it says port only and the other is the UDP tracker port. So which one should I write down?

Thanks for your response

pookito wrote:Ok guys, here is my problem. I have been trying to make this work for the longest time. Since I last posted. And still I can not get ktorrent to work and share files. I give you an example. for the tracker I do the ip address plus the port. Something like this: http://xxx.x.x:444/announce. I try the other torrent client and add my ip address and port. Well, it does not work. After several attempts I noticed on the "trackers tab" a message that says: "Could not connect to host xxx.xxx.x.x: Connection refused." So, Am I supposed to have that problem? Or can I do something else to fix it?

What exactly are you trying to do ? Where is the tracker running ? Are you using your local IP address for the tracker ?

I tried that last time and it worked (DHT-only).
The key is to add your public ip address to DHT nodes and your incoming port, right?

Also sometimes (rarely) ktorrent automatically adds some ip's under DHT nodes when creating
decentralized torrent, but not always. I'm not sure why.

I tried the suggested steps to move a 60GB music collection simply on a lan - but the peer kept being "choked" and disappearing - nothing would download. Using KTorrent v4.3.1 on KDE Development Platform 4.13.3