First, many thanks for such a great application!
In adanced options, I use privoxy/tor as HTTP tracker proxy and "do not use the KDE proxy for HTTP tracker connections", but when I stop tor, I still get peers for the running torrents.
How then can I make sure that ktorrent is really using privoxy/tor?
Many thanks in advance,
jean-luc

Have you disabled DHT?

>Have you disabled DHT?
No: I'll try. Thanks.

Unfortunately, no change...

The best way to check is via ethereal (wireshark) or some other traffic sniffing utility.

I'm guessing that this is a result of other clients who have talked to the tracker BEFORE you stopped the torrent are now trying to connect to you based on their stale data.

I have checked with "privoxy --debug" and I see no connection attempts with ktorrent whereas they clearly appear using firefox, so it seems the proxy is not used at all.
>I'm guessing that this is a result of other clients who have talked to the tracker BEFORE you stopped the torrent are now trying to connect to you based on their stale data.
I have witnessed the behavior when starting with a fresh torrent, but I will check again tonight.
I am using 2.1.4 from Fedora 6 Extras, which was built (I checked) using:
configure \
--disable-rpath \
--enable-new-ldflags \
--disable-debug --disable-warnings \
--disable-dependency-tracking --enable-final
Anything else I can do to help debug the problem?
Thanks very much for your help.

I have checked with "privoxy --debug" but with the global KDE proxy set to privoxy/tor (with "do not use the KDE proxy for HTTP tracker connections" unchecked) and I see tracker traffic. Should I report the bug and where?

This just a bunch of peers who still have your IP address.

I have checked with "privoxy --debug" and I see no connection attempts with ktorrent whereas they clearly appear using firefox, so it seems the proxy is not used at all.

The tracker is not contacted very often, and most trackers set a rather long update interval (30 minutes or more). If you want to be sure, do a manual tracker announce and then check privoxy. Then you are sure KT is actually connecting to the tracker.