search

xlgjjff / libtorrent

Automatically exported from code.google.com/p/libtorrent
Other
0 stars 0 forks source link

Return Proxy External IP address in error message when initial connection attempt fails #678

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi Arvid, I have started quite the discussion over in the qBittorent forums 
regarding this issue. The bottom line is that you are the only one that can 
answer this. I think this can be done. Can you please have a look at this post. 
Thanks... 

http://qbforums.shiki.hu/index.php/topic,2778.0.html

Original issue reported on code.google.com by gsoud...@cox.net on 24 Sep 2014 at 5:18

GoogleCodeExporter commented 8 years ago 
Arvid, Is this even possible if the initial connection to the proxy fails? The 
guys in the forum thread indicate that it is not.

Original comment by gsoud...@cox.net on 25 Sep 2014 at 9:18

GoogleCodeExporter commented 8 years ago 
it's a bit confusing what "proxy external IP" refers to. it sounds like it 
would refer to the proxy's external IP, but I get the sense that that thread 
mean to say the client's external IP.

the client's external IP is only available after someone has reported it. i.e. 
a tracker (not likely), a DHT node (quite likely) or a peer (quite likely). 
Before then, the client cannot know its own external IP.

If the IP refers to the proxy's IP, it will not be known until the hostname 
resolves successfully.

Original comment by arvid.no...@gmail.com on 25 Sep 2014 at 9:47

GoogleCodeExporter commented 8 years ago 
It is the IP of the resolved hostname that is used to communicate with the 
Socks Proxy provider. I am using a hostname as opposed to a hard coded IP in 
qBittorrent settings. As you state this has to be resolved before a connection 
attempt can be made to the Proxy Server. In Issue 613 comment #4 you state "the 
proxy hostname is always resolved using the normal system hostname resolver".

Sometimes my proxy provider returns "no connection could be made because the 
target computer actively refused it". This is happening randomly on some of 
their IP's. I am working with them to resolve the issue. In the case of 
successful connection the qbittorent logs shows and access denied message. I am 
not sure why this is. In either case or any other socks error event, it would 
be nice to display the resolved IP that was used when the error occurred. 
Currently all socks error messages display 0.0.0.0 for the IP.

Original comment by gsoud...@cox.net on 25 Sep 2014 at 11:51

GoogleCodeExporter commented 8 years ago 
Arvid, is there any progress on this issue?

Original comment by gsoud...@cox.net on 11 Oct 2014 at 10:12