Difference between revisions of "UsingBitTorrentThroughProxy"

From Theory.org Wiki
Jump to: navigation, search
m (Removed spam. (Advice from a spammer is not trustworthy and also removed.))
 
Line 97: Line 97:
 
I'm a system administrator, and I'd like to make [[BitTorrent]] available through a proxy that understands the [[BitTorrent]] protocol and can even cache requested files locally and serve them up... but of course I want to be able to control access to them as well. Is there anything like that out there? If not, one of you smart guys ought to do something about that. -- [[RevArgent]]
 
I'm a system administrator, and I'd like to make [[BitTorrent]] available through a proxy that understands the [[BitTorrent]] protocol and can even cache requested files locally and serve them up... but of course I want to be able to control access to them as well. Is there anything like that out there? If not, one of you smart guys ought to do something about that. -- [[RevArgent]]
  
 
<br>
 
<br>
 
 
----
 
----
Hmm this is somewhat outdated,i am going to add a few hints and tips here if you guys do not mind.
 
----
 
 
First you need a reliable and trustworthy service like mine ;)<br>
 
To avoid any misunderstanding http://www.gtguard.com is a payed service do<br>
 
not trust ANY free service who knows what they do with your data!<br>
 
<br>
 
Usually a bittorrent proxy is using a socks5 server to connect you<br>
 
to other peers in the bittorrent swarm that usually happens<br>
 
without you noticing it, some users have reported that they even<br>
 
use bittorrent faster than without a proxy.<br>
 
<br>
 
Note to other socks versions:<br>
 
Do not use other versions ( version 4, version4a)<br>
 
they do not support all the features a bittorrent client requires!<br>
 
<br>
 
Lets get to the basics:<br>
 
you need an account<br>
 
to get the details for you bittorrent client<br>
 
then you have to enter them into the proxy settings of your client,<br>
 
these are the hardest parts a user has to do ;)<br>
 
<br>
 
To have the fullest protection your service needs to support<br>
 
the so called "p2p connection over proxy" that only means<br>
 
that the connections downloading the parts from other peers <br>
 
are handled by the proxy as well and nothing more!<br>
 
<br>
 
After entering out your details you need to double check them<br>
 
if there correct ( Please ;) )<br><br>
 
These details include the following,<br>
 
a proxy server url or IP the port the proxy is listening on<br>
 
your username and password and the socket typ the server are using<br>
 
<br>
 
Then you are ready to go.<br>
 
Use a torrent of your choice and see if that works.<br>
 
If not ( that does happen ;) ) you need to check your<br>
 
firewall antivirus or any related software if the <br>
 
port given is blocked or closed by it.<br>
 
(Please consult the manual about those issues)<br>
 
<br>
 
If finally those issues are solved you should<br>
 
enjoy your bittorrent downloads without the fear of being<br>
 
spied on or otherwise being disturbed.<br>
 
<br><br>
 
One thing about "Good" or "Bad" services:<br>
 
Do they have service, and do they care about there customers ?<br>
 
Do they answer questions regarding payments or<br>
 
even help you set up?<br>
 
All those things are valuable information for you to<br>
 
decide what service to use.<br>
 
 
With best regards <br>
 
Mike<br>
 
 
 
Back to [[BitTorrentFAQ]]<br>
 
Back to [[BitTorrentFAQ]]<br>
 
Part of [[[[Category:BitTorrent]]]]
 
Part of [[[[Category:BitTorrent]]]]

Latest revision as of 22:07, 7 October 2013

Problem Connecting to tracker - HTTP Error 407 Proxy Autorization Required....

'Note: There is currently no way to do this


It would be great to add a feature so we can choose which proxy like in a browser to use with bittorent and download the files through a proxy.


BitComet works with HTTP proxies. But it is usually blocked in most Unis (HTTP CONNECT)


Using SocksCapv32 with BitTorrent it is possible to "socksify" BitTorrent using sockscap.

'socks cap doesnt work for me but i ve seen an interesting way to do it in some p2P app here it is

When client is unable to communicate with the server using plain TCP connection, HTTP tunneling can be utilized to access the Hotline server over an HTTP proxy. To accomplish this, the client creates two connections to the server. One would be used for sending, and other for receiving data. After these connections are open, the client begins transmitting standard HTTP requests. If HTTP proxy terminates connection while that connection is still in use, the client recreates them, and interrupted requests are resent.

HTTP Requests

HTTP POST request is sent over sending, while GET request is sent over receiving connection. The POST request is specified as follows:

POST <address> HTTP/1.0

Proxy-Connection: Keep-Alive

Pragma: no-cache

Host: <host>

Content-Length: 999999999

Content-Type: hotline/protocol



The server replies to this request at the time when connection is about to be closed, as:

HTTP/1.0 302 Found

Connection: close

Content-Length: 8

Content-Type: hotline/protocol



Next 8 bytes are filled with 0 to indicate termination of a connection.

GET request is specified as:

GET <address> HTTP/1.0

Proxy-Connection: Keep-Alive

Pragma: no-cache

Host: <host>

Accept: hotline/protocol



Server�s immediate reply to GET is:

HTTP/1.0 200 OK

Proxy-Connection: Keep-Alive

Content-Length: 999999999

Content-Type: hotline/protocol



After this reply, server uses this connection to send data to the client.

Address used in these requests is standard URL address followed by the session ID, specified as the file in the root directory. This is an example of such address:

http://tracker.com:5497/5555-5555-5555

Session ID is used in order to identify the client in the case of disconnect. Host name specified in the HTTP headers is in the form of standard domain name string, followed by the port number. For example:

tracker.com:5497


I'm a system administrator, and I'd like to make BitTorrent available through a proxy that understands the BitTorrent protocol and can even cache requested files locally and serve them up... but of course I want to be able to control access to them as well. Is there anything like that out there? If not, one of you smart guys ought to do something about that. -- RevArgent


Back to BitTorrentFAQ
Part of [[]]


Last edit: Fri, 14 Jul 2006 13:42:10 -0700
(WikiWord)
Revisions: 17