I'm attempting to seed a torrent, and it's 'uploading' at 0.0 KB/s.

I've checked my router and uPnP is enabled as well as the uPnP plugin in ktorrent. According to the options screen for the plugin, 6881 (TCP) and 4444 (UDP) are being forwarded. I've telnet'ed in to the TCP port using the external address, so I know that it is forwarding.

When I looked at the packet dump in ethereal, there was handshaking and other protocol information sent, but no actual file data.

How many leechers are in the swarm ?

rasactive wrote:I'm attempting to seed a torrent, and it's 'uploading' at 0.0 KB/s.

I've checked my router and uPnP is enabled as well as the uPnP plugin in ktorrent. According to the options screen for the plugin, 6881 (TCP) and 4444 (UDP) are being forwarded. I've telnet'ed in to the TCP port using the external address, so I know that it is forwarding.

When I looked at the packet dump in ethereal, there was handshaking and other protocol information sent, but no actual file data.

most sites dnt accept port as 6881.
uyse ports in d range frm 7000------65000

6881 is the worst possible port as he said. If you have actual leechers, almost every isp known to man throttles 6881 either on your end or their end for any connection that attempts to reach 6881. Some ISPs seem to even secretly block 6881 as in they will allow a connection to be established and then block any subsequent data packets. A few iISPs used to do that to port 1214 in the Kazaa days. Try port range of 49512-65535 and turn on protocol encryption. PE is one reason I came to ktorrent in the first place and I appreciate its implementation.

PS-The problem does not seem to be his tracker. Otherwise he'd likely get a message in tracker status sort of like "Rejected by tracker. Port xxxx is blacklisted"(xxxx in his case might read 6881 on some trackers).