I have KTorrent 2.2.2 on PCLinuxOS2007. Several Questions (I am a KTorrent n00b, sorry):

1) Today I downloaded a 470MB torrent of Enemy Territory: Quake Wars Full Linux Server, no problem! But KTorrent is still showing 0 bits Uploaded after 3+ hours at Status = Seeding. KTorrent Upload tab currently shows " Seeders 0(10)". So I'm not sure if my Upload is actually enabled. I tried Manage by QM (queue manager) and manage by User, but still no bits uploaded. I installed and enabled the UPnP Plugin for KTorrent, and ensured ports 6881-6999 are forwarded for TCP&UDP on my Router. KTQueue Dialog says "Status: Seeding" and "DHT: Yes", and includes a URL to Tracker site "http://zereowind.id...om:6969/announce". I'm ASSUMING that after 3+ hours, somebody else would have requested this new gane server Torrent). I'm on Comcast cable internet, do they maybe block torrent uploads? In short, IS my KTorrent ready and willing to Upload??

2) I don't have the KTorrent/KDE HTML Help file (not in /usr/share/doc/HTML/en/ktorrent.......or anywhere else). Is this available for download somewhere?

Thanks in advance.

Well, presumably there are no leechers for this file. You can only upload to leechers, obviously, as seeders have full copies of the files. Try with some different file, known to have leechers.

As far as I know, there is no documentation available, although I recall reading someone's been working on it.

Thanks for reply lucke.

On your point that maybe nobody had requested the torrent for download, I fired up my Windoze PC and downloaded the torrent that my Linux PC was concurrently offering to Upload via KTorrent. My KTorrent howver still showed 0 bits uploaded, leaving me still unsure if my KTorrent is really ready and able to upload. Whilst downloading the 418MB torrent to Windoze, KTorrent showed Leechers "0(1)", Seeders "0(10)" and Status "Seeding". I tried both User Controlled and QM Controlled in Queue Manager dialog.

Should I expect for this actual scenario that KTorrent would show some bits/bytes sent, if working properly?

TIA.

Could be that your Windoze PC was the denoted 1 leecher, although apparently it didn't choose to download anything from your PC with KTorrent.

Just go to isohunt.com, type anything that comes to your mind, find a torrent with a decent amount of leechers and see how it works. If you get incoming connections, there should be no icon in the bottom left corner, on the statusbar - although even without incoming connections you should be able to upload.

Google Comcast and Sandvine and you will read a lot of notes from people that believe Comcast is preventing seeding.

There are 2 fixes I read about:

http://thaking.net/pages/comcast-fix/

ecently, Comcast has stopped the seeding of torrents. (More details here)

Basically, what they're doing is telling your computer it needs to close it's TCP connection at a certain port (in this case, your torrent clients' port) via the RST TCP reset command.

Since they're using such basic methods to stop seeding, there's a simple way to stop them from stopping you. Although I have no fix for the Windows operating system, in Linux, it's a simple fix. Every modern Linux distribution has iptables, so all you have to do is set it up to block this RST command. This should also work in BSD systems, Mac OS X, or any system with iptables.

All you have to do is run the following command, with superuser privileges (sudo, fakeroot, a super user terminal, etc). The one thing you need to do, is change the word $port to whatever port your torrent client uses.
Run in your shell/terminal: iptables -A INPUT -p tcp --dport $port --tcp-flags RST RST -j DROP

Also, should you ever need to remove this, all we need to do is make that A (for Append) a D (for Delete). The resulting command would be:
Run in your shell/terminal: iptables -D INPUT -p tcp --dport $port --tcp-flags RST RST -j DROP

In addition, I believe that if you have a router running some variant of Linux (DD-WRT, Open-WRT, etc), this trick should work on that, since all we're doing is dropping RST commands.. All you should need to do is ssh or telnet into your router and run the command with the appropriate port, however, I haven't tested this, so do this with caution.


I tried this but it leaves a lot of connections messed up in Ktorrent, may have several peers with the same ip address in ktorrent.

***********

the other fix is:
http://redhatcat.blogspot.com/2007/09/b ... ables.html





Having wrote all that, I have been having trouble uploading at a private tracker called GOEM. I read about another individual that gave up on ktorrent so I tried uploading and it did nothing. I downloaded 2.2.2 and installed that and it would upload in short bursts, but for the most part nothing. I am not sure where the problem is because at piratebay I can download and upload to my full 90KBs but not so good on GOEM or now Clawtorrents.

It has been a frustrating week or two for me, as my favorite tracker "Smoking in the Rain" banned Ktorrent and finding another tracker I like just isn't working out as well as I would like. It all becomes more complicated knowing there might be a problem with ktorrent as well as Comcast.
Whereas I was able to fullfill my seeding requirements in a couple days, now it looks like it will take weeks and my systems just can't handle that many seeds at one time. I may be stuck to switch to another bit torrent client or to just hit and run public trackers only - neither option is desirable to me.




[url][/url]

on edit:

I just worked a file on Oink as I know Ktorrent works there and the download was at maximum speed for my system about 1000KBs and upload was at my max about 90KBs until the download stopped then Sandvine kicked in and although there were close to 40 leechers, I was not connected to any, and after I restarted the torrent I could see the peers connect then disappear - the rests went up:

@ubuntu:~$ netstat -s | grep -i resets
10126 connection resets received
8588 resets sent
4 resets received for embryonic SYN_RECV sockets
@ubuntu:~$ netstat -s | grep -i resets
10140 connection resets received
8592 resets sent
4 resets received for embryonic SYN_RECV sockets


my iptables for the ktorrent port:

0 0 ACCEPT 0 -- lo * 0.0.0.0/0 0.0.0.0/0
20 800 DROP tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:52000 flags:0x04/0x04
47935 10M ACCEPT 0 -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
203 10380 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:52000
78 3382 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:52000
400 113K REJECT 0 -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibit

I did bump into 1 peer using Azureus, most others were using Utorrent that stayed connected and also downloaded at my maximum speed until it was near completion.


On Oink the forums suggest that both clients must be set up to ignore the rst or the connection will be lost.


Perhaps the bit torrent clients should keep track of the "availabilty" and if it is less than 100% to ignore rst. Another idea would be to work much like automatic garage door openers with rotating codes ( along with encryption) so that rst commands would be ignored without the proper code attached, and as with garage door openers, the code would change each time the packets are exchanged. This would put mch more stress on the Comcast system to figure out what was going on. I think that if you can force them to come out in the open so people all know what they are doing, the customers will put a stop to it. Right now too many people are far more trusting then than should be, they believe Comcast ( and others) are doing what is best for all, rather than just making more money.

lucke wrote:As far as I know, there is no documentation available, although I recall reading someone's been working on it.

That is right, i am working on that. It will be on the forums for review soon so we can all review the doc for some time.

@ Stoepegel:

Just wondering now (3+ years later) if you or others have posted the requested documentation? If so, please provide a link to it.

A few days ago on a newer PCLOS install, I set up KTorrent and tried seeding. Had no uploading at first, then I modified port forwarding on my routers (my PCLOS box is on a downstream router) to forward my specified KTorrent port (6881) to my PCLOS box. After awhile, finally *did* get a little bit of upload traffic (just a few 100Mib is all, over 1-1/2 days). Meanwhile, my Windows 8 box (on the upstream router) running uTorrent with the same PCLOS torrents pumped out >1GiB in just 1/2day. Any thoughts on why the KTorrent did relatively poorly? Might I have overlooked some critical KTorrent setting needed for better / faster upload traffic?