Problems Passing Peer2Tracker (P2T) connections as HTTP through Tor

http://img443.imageshack.us/img443/1...ckerurlfr3.png http://img152.imageshack.us/img152/1...erencesbm8.png

i am trying to route all my p2t connections through privoxy and tor in, it seems, vain. vidalia shows no traffic in its bandwidth graph. the torrents update with the tracker correctly in this configuration with or without the presence of privoxy and tor. it seems like these proxy settings aren't doing anything at all.

i have tried the same thing with a torrent that announces to the http tracker of waffles (just substitute https with http in both images). it doesn't want to work!

i have tried even shutting down privoxy and tor with these settings on and the tracker status still updates fine.

i am utterly confused...

can you post your privoxy config file plz.

also here is my azureus tor proxy setup:

http://img38.echo.cx/img38/2520/azprivoxy3hn.jpg

awesome, a fellow tor-user :)

madbeer, my privoxy config file hasn't been altered. listening port is still 127.0.0.1:8118

wont this slow down your torrent speed ?

I am only proxying (I hope this is a word) my tracker communication. My peer-to-peer traffic uses no proxy.

Since I use comcast I am experimenting using tor to prevent their mangling of my connections. No clear results yet...

Quote:

---

Originally Posted by FatBob

wont this slow down your torrent speed ?

---

we are only passing http traffic through tor, so as to rid our real ip address from the logs of the tracker.

madbeer, shall i try azureus? if so, which version?

$we, why are you using privoxy?

I only use tor + azureus, but you can you use any bt client that supports proxying.

Change your proxy type from HTTPS to SOCKS, and set the Proxy Server Port to be the port you configured Tor to listen on locally (in that old screenshot I posted Tor was listening on port 8118)

Quote:

---

Originally Posted by madbeer

I am only proxying (I hope this is a word) my tracker communication. My peer-to-peer traffic uses no proxy.

---

how do you do that ?

Quote:

---

Originally Posted by madbeer

$we, why are you using privoxy?

I only use tor + azureus, but you can you use any bt client that supports proxying.

Change your proxy type from HTTPS to SOCKS, and set the Proxy Server Port to be the port you configured Tor to listen on locally (in that old screenshot I posted Tor was listening on port 8118)

---

yes, but then what is stopping all the bittorrent traffic from running through tor?

edit: ok, i have done what you have recommended, madbeer, and my download speed is now considerably lower than normal, although not at all disagreeable. I mean, I could live with it, but it has confirmed that all traffic is now routing through the tor network.

edit#2: scratch that, lol, i accidentally checked p2p connections. how can i confirm that only the p2t connections are passing through tor now?

Quote:

---

Originally Posted by madbeer

<font face="arial" size="2">can you post your privoxy config file plz.

also here is my azureus tor proxy setup:

http://img38.echo.cx/img38/2520/azprivoxy3hn.jpg

---

madbeer... why did you change the listening port of tor from 9050 to 8118?

You can install Ethereal (wireshark), and watch the traffic to make sure its getting proxied. All tracker communications will be sent over the proxy, and all p2p communication will be sent directly to the peers.

I'm using port 8118 in that screenshot just as a test, I had configured tor to listen on that specific port

Now for why anyone would want to do this:

If the tracker site gets raided, and an organization checks the server logs; people who use tor for tracker communication would be protected from IP address identification. Although, you would also need to use tor (and potentially privoxy) when browsing your favorite trackers content on the web (to remain completely anonymous from the trackers point of view). The downside to this whole thing is latency through the tor network, trackers banning you cause your IP always changes, and MAFIAA like organizations who actually attempt to connect to you as a legitimate peer will be able to implicate you in file-sharing. (there is software you can get that has blacklisting functionality -- peerguardian and others)

If you wanted to tunnel tracker communications over HTTP and _then_ to TOR (like your thread title suggests), you can set up httptunnel (http://www.nocrew.org/software/httptunnel.html) on your home machine and some endpoint node in a different network, then initiate the TOR tunnel at your httptunnel end point.

There are of course, other things to do to hide.....