Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

2.35-a6 self connect twice

by Guest on 2016/04/29 11:49:07 PM    
hello,

2.35-a6 win32, got some ip in peer list completely different from mine (even country flags are different), refused connection because of "self connect"

i.e. i got two "self connect" statuses in single torrent: one is mine and correct, other is not mine and wrong.

both of us using tixati with PeerID starting with tix0235-

thanks.
by Napsterbater on 2016/04/30 02:50:33 AM    
What is the IP that is not you?
by Bugmagnet on 2016/04/30 07:33:26 AM    
with v2.35-a7 I had 5 rejected self connects showing and reported that anomaly to the DEVs.

3 were mine. I have a dual WAN connection and in addition to those 2 IPs, the LAN IP of the router, (192.168.x.x) was also showing as a 'self-connect' as well as the IP of my channel client.

As to the other 2, they had the same PORT as a uTorrent client that was connected and all these 3 had different IP blocks:
72.132.x.x connected
68.116.x.x self connect
24.43.x.x  self connect

My 2 WAN IPS were on different A blocks than those 3.

with v2.38, I no longer see any self-connects from my router IP of 192.168.x.x and I did not see any foreign self-connects from other users after examining about 50 active torrents. Perhaps the underlying quirks have been fixed. I didn't recognize any item on the change log for this issue so maybe it was done under "numerous other minor GUI fixes and improvements" :)




This web site is powered by Super Simple Server