see, you said it your self if its never used why doesn't it make the throttle go away after ? so just like i said they do check for rc4 and and the other factors..Originally Posted by The248
already disabled scrape and since im at userenity i disabled updates long ago..
what do you mean?
You said tixati gets throttle just by opening uTorrent (without starting any torrent) this means it can't be rc4
rc4 it's only used on peer to peer connections, just opening utorrent doesn't start any peer to peer to connection
furthermore tixati uses the exact same rc4 as any other bittorrent client, if they are detecting rc4 tixati would be throttle as well
but they don't use the same configuration timeouts and size of exchanging encrypted RC4 packets and further more clients like deluge let you modifie the header or encrypt the full stream so obviously they're not the same as you say..
the algorithm is one factor but its not just about it
Last edited by n4overclock; 24.03.12 at 15:07.
You said tixati starts to getting throttle when you open utorrent
just opening utorrent doesn't generate rc4 on utorrent, how can they detect something that still doesn't exist?
we came to the conclusion that tixati works well, but if you open utorrent (just opening) it triggers a switch on the isp that then starts to throttle every bittorrent connection
how can that be rc4 related?
or did i miss read what you wrote on previous posts?
that's the wrong question .. the right question is why tixate can't work without RC4.. so if it was only about something like tcp packet size or the way peers handshake it should be no problem right? because the isp don't check for RC4 right ? well tixate gets throttle if no forced encryption
so no matter how many factors they take to flag a mac for rc4 traffic throttle.. RC4 is always gonna be 1 of them if they previously decrypted few packets and found to be be having bittorrent data inside
something as simple as
127.0.0.1 bittorrent.vo.lhwd.net
127.0.0.1 update.utorrent.com
127.0.0.1 apps.bittorrent.com
could trigger the throttle and should be put to 127.0.0.1
utorrent
tnx for participating in this.. and i would make tutorial if get time soon..
Last edited by n4overclock; 24.03.12 at 18:52.
How easy is to detect a bittorrent connection that after connecting sends immediately "Bittorrent Protocol" in plain text? do you think a isp that gives itself the trouble of trying to block rc4 wouldn't implement that little check?
if they did check every connection for rc4 then tixati would be throttle aswell
your isp is not detecting tixati rc4 (because you don't get throttle), then you open utorrent (no connections started = no rc4), tixati gets throttle
^^^^ how can the isp be checking for rc4 at this point?
that's an easy thing to say but like i said thousand times before not all packets and the way they are configured are the sameif they did check every connection for rc4 then tixati would be throttle aswell
think of it as wireless cracking you don't always use the same parameters and attack methods to crack the same rc4 right ? right ? ^^ and so are those 2 differently configured clients
the isp gotta synchronize with the way data is passing trough in order to decrypt it
Last edited by n4overclock; 24.03.12 at 19:03.
i would accept that explanation if tixati would be randomly throttle
but from what you've reported tixati works fine all the time until utorrent open
do this test:
- remove all torrents from utorrent list
- put tixati to work
- start utorrent (without any torrent on the list)
- restart tixati connections
from you've reported you should see trottle, please confirm
then do this test:
- block utorrent 100% on the firewall (meaning utorrent doesn't access any internet)
- put tixati to work
- start utorrent (without any torrent on the list)
- restart tixati connections
tell me what you get from those two tests
what are you talking about ? why would i do that when i know for a fact that my utorrent is working correctly after i've done the changes for it to work just like tixati ? and the fact that they both fail even with their forced rc4 when my mac gets flagged on purpose; looks like you've missed a post
Last edited by n4overclock; 24.03.12 at 19:26.
lol you've edited it
So this is the problem:
127.0.0.1 bittorrent.vo.lhwd.net
127.0.0.1 update.utorrent.com
127.0.0.1 apps.bittorrent.com
what did i tell you? you only get throttle after you being flagged
for you to be flagged they need to detect you in a "affordable" way
if you are into digging deeper, try 1 by 1 those urls until you find with one (or more that one) flags your mac
what about udp? does it work?
basically is forcing encryption and blocking those addresses, that's all?
nop only encrypted tcp should be enabled.. you should already know this because tixati doesn't connect to those urls but fail if i allow udp.. im not sure about dht since i got it on disabled for years nowlol you've edited it
So this is the problem:
127.0.0.1 bittorrent.vo.lhwd.net
127.0.0.1 update.utorrent.com
127.0.0.1 apps.bittorrent.com
what did i tell you? you only get throttle after you being flagged
for you to be flagged they need to detect you in a "affordable" way
if you are into digging deeper, try 1 by 1 those urls until you find with one (or more that one) flags your mac
what about udp? does it work?
basically is forcing encryption and blocking those addresses, that's all?
Last edited by n4overclock; 24.03.12 at 19:53.
So resuming, to avoid throttle on your isp:
- bt.transp_disposition = 5
- forced bittorrent encryptation + don't allow incoming legacy
- block, bittorrent.vo.lhwd.net + update.utorrent.com + apps.bittorrent.com
yes and also no nat-pmp + upnp tcp only (true) and the mac should be fresh
it might be very helpful if the modded clients come with a choice to block those url's like a value in uSerenity Settings.exe or a dedicated version for anti-throttle
Last edited by n4overclock; 24.03.12 at 22:11.
I think you can safely enable UPnP and NAT-PMP without problems
give it a try and let us know how it works
it doesn't work .. and to clarify things a bit im not talking about disabling UPnP im talking about the open no udp port option in the advanced configuration which is "upnp tcp only" at "true" it comes at false by defaults, noobs got trolled %)..
Last edited by n4overclock; 26.03.12 at 23:58.
Posting Permissions
Reply With Quote
Bookmarks