the specific trackerfiles still work ? like the previous version had IPT & TL specific client files
Printable View
the specific trackerfiles still work ? like the previous version had IPT & TL specific client files
Would this leeching majig work on something like waffles for example or pretome.
With a static IP...this method would not work very well for is that correct?
It works but it isn't perfect because then they can search after the ghostleeching ip of their client which isn't in the peerlist at the tracker and find your account...
That's for the old RM, and new versions have fixed this.
It most likely works at Pretome. I don't know about Waffles, but I wouldn't recommend you try it.
What Butcho said.
But if the tracker doesn't ban proxies you could make the only announce from behind one - have a look at the semi-anonymous torrenting tutorial in my sig.
I think anon u should put one of this mod in every new utorrent mods .
I don't know... the procedure to use the ghostleeching mod correctly would make the post twice as long :biggrin:
On the other side, I could link to this thread or a tutorial, but for some reason I think this method deserves a separate spot.
By the way, I'll update this mod soon :wink:
I didn't forget... was just waiting a bit between releases :smile:
And there'll be a 1.9-based mod too. :top:
Does this maybe work on version 1.8.1.?
Not until I make a v1.8.1 ghostleeching mod :biggrin:
I plan to update this soon, will also add that version and 1.9, then.
I see. Then I need your help anon. I did download version 1.8.2. but it didn't work fine, something with connecting to seeds and peers. You allready once gave me the solution, but I can't remember where is now, all I know that I had to change something in settings. So if you know what I'm talking about, plz write it again. :redface:
You mean this?
Quote:
In 1.8.0 - 1.8.2, bt.transp_disposition controls which transport is used for outgoing connections only (that is, it doesn't filter incoming connections). The values are interpreted as follows:
0: attempt only TCP
1: attempt both TCP and uTP, drop TCP if uTP is successful
2: attempt uTP if supported, TCP otherwise
3: attempt only uTP
I'm not sure! I have value 255 in my settings!
255 means using both TCP and uTP. Try setting it to 0.