the third p2p downloader can't recognize libttorent connection

[GoogleCodeExporter]

What steps will reproduce the problem?
1.run my application support bt download with libtorrent, download speed is 
70kb/s
2.run bitcomet open the same torrent to downloading, speed alomost is 70kb/s
3.I found the user list of bitcomet has not the ip of myappliacton
4.I add the ip that my application is running to the user list of bitcomet 
manually, sosososo,the speed of my application download is 2MB/s

What is the expected output? What do you see instead?
why bitcommet can't connect my application with libttorent automatically?

What version of the product are you using? On what operating system?
0.16.13

Please provide any additional information below.
bitcomet is a p2p downloader run in windows, it has a user list that can be 
added user into.

I am sorry,my english is poor...

Original issue reported on code.google.com by qia...@gmail.com on 27 Dec 2013 at 7:15

[GoogleCodeExporter]

it's not obvious from the description that libtorrent _can_ make bitcomet 
discover and connect to it. Is there any details in your setup that makes you 
expect that it would?

does bitcomet support local peer discovery? (if so, did you wireshark any of 
its packets?)
are you connectable via your external IP? (if so, would you expect the tracker 
to prioritize peers from the same IP?).
Do you expect the tracker to track more than one peer per IP? (afaik, the most 
popular tracker, opentracker, only tracks one peer per IP, for spoofing 
reasons).

Original comment by arvid.no...@gmail.com on 27 Dec 2013 at 9:01

[GoogleCodeExporter]

thank you for your reply.

[1]I run my appliation in one computer named A,and run libtorrent in another 
computer nmed B(it is a stb).
[2]A and B are behind router, there's IP are automatic allocation.
[3]A and B are downloading same torrent file.

--Is there any details in your setup that makes you expect that it would?
I configure libtorrent as normal, do nothing special.

--does bitcomet support local peer discovery? (if so, did you wireshark any of 
its packets?)
I haven't wireshark it.I just think p2p protocal is standard, so applications 
who implement the protocal should discrover each other. is it true? 

--are you connectable via your external IP? (if so, would you expect the 
tracker to prioritize peers from the same IP?).
libtorrent and bitcomet are both behind router.
I don't expert tracker can prioritize peers from the same IP. I expect bitcomet 
and libtorrent can discover each other.

--Do you expect the tracker to track more than one peer per IP? (afaik, the 
most popular tracker, opentracker, only tracks one peer per IP, for spoofing 
reasons).
if tracker only tracks one peer per IP, those computer behind router how could 
download files, because they have the same public IP.does NAT not work in here?

sorry again for my poor english.

Original comment by qia...@gmail.com on 27 Dec 2013 at 9:36

[GoogleCodeExporter]

> I haven't wireshark it.I just think p2p protocal is standard, so applications 
who
> implement the protocal should discrover each other. is it true? 

I don't know if bitcomet implements local peer discovery. It wasn't part of the 
original specification, so it's possible it doesn't. Local peer discovery is 
also sensitive to the setup of the local network, as it depends on multicast 
support. Some networks simply block multicast.

> if tracker only tracks one peer per IP, those computer behind router how could
> download files, because they have the same public IP.does NAT not work in 
here?

It works because in most cases it's not critical that peers behind the same IP 
can connect to each other, they can complete the download from other peers.

Original comment by arvid.no...@gmail.com on 27 Dec 2013 at 5:00