search

frostalf / libtorrent

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

Too Many IP Blocks #575

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This has to do with a torrent client called qBittorrent, which is a wrapper of 
this libtorrent C++ library.

What steps will reproduce the problem?
1. Open qBittorrent
2. Start downloading some "popular" torrents.
3. Open from the menus, the Execution Log screen.
4. Click on Blocked IPs on the right.

What is the expected output? What do you see instead?
I would expect to see (maybe?) not so many IP blocks.
I see VERY often IP blocks, like sometimes many in one second.

What version of the product are you using? On what operating system?
Win7 32bit Home Premium.
qBittorrent v.3.1.5 using
libtorrent 0.16.13.0 and
boost 1.55.0

Please provide any additional information below.

In qBittorrent forums and bug trackers, I was told that this is a feature of 
libtorrent. And there are several reasons for this:

1. the IP filter (I have disabled this in qBittorrent)
2. i2p mixed mode restrictions (a normal peer is not allowed on an i2p swarm)
3. the port filter
4. the peer has a low port and no_connect_privileged_ports is enabled
5. the protocol of the peer is blocked (uTP/TCP blocking)

The thing is, that I would like to report, that in my case, the IP blocks, as 
seen in the Execution Logs Blockes IPs, are VERY many, and they happen like 
every 5th second, sometimes every second, at best every 3rd minute. Or stuff 
like that.

Could you kindly tell me if this is the expected behaviour?

Original issue reported on code.google.com by chaos.ta...@gmail.com on 3 Feb 2014 at 9:30

GoogleCodeExporter commented 9 years ago 
what does it mean by seeing many IP blocks?
what property or event of libtorrent is that?

Original comment by arvid.no...@gmail.com on 4 Feb 2014 at 10:30

GoogleCodeExporter commented 9 years ago 
Let me clarify. The blocks reported in the gui are in reaction to 
'peer_blocked_alert'.

Original comment by hammered...@gmail.com on 5 Feb 2014 at 8:51

GoogleCodeExporter commented 9 years ago 
this alert is not just posted because of an IP being blocked. when you say "the 
protocol of the peer is blocked", you mean the peer that you get a 
peer_blocked_alert for?

I would have expected it to be intuitive that if you block uTP or TCP (blocking 
both seems pointless), any peer trying to connect to you over the blocked 
protocol will be blocked, and potentially post a peer_blocked_alert.

Original comment by arvid.no...@gmail.com on 5 Feb 2014 at 9:54

GoogleCodeExporter commented 9 years ago 
however, it's probably a good idea to add the reason of a peer being blocked in 
the alert.

Original comment by arvid.no...@gmail.com on 5 Feb 2014 at 9:54

GoogleCodeExporter commented 9 years ago 
@arvid, you don't expose the reason in the alert....

Original comment by hammered...@gmail.com on 6 Feb 2014 at 12:14

GoogleCodeExporter commented 9 years ago 
Found that page while googling. I have the same trouble.

What steps will reproduce the problem?
As in OP-post.
Downloading some torrents as usually. Then at random moment all connections 
blocking. Any new connection blocking too. Torrents actually stop downloading. 
That until qBittorrent restart.
Message in log is like this: 07/02/2014 01:00:27 - 123.123.123.123 was blocked

What is the expected output? What do you see instead?
As in OP-post.

What version of the product are you using? On what operating system?
Win7 x64
qBittorrent v.3.1.8 (with Qt 4.8.5, libtorrent 0.16.14.0, boost 1.55.0)

Please provide any additional information below.
In qBittorrent "Use UPnP / NAT-PMP port forwardingfrom my router" is enabled.
My computer connecting to Internet using router that running miniupndp with 
enable_natpmp=yes, enable_upnp=yes and secure_mode=no. It don't throws any 
error or warning messages and all other upnp software works ok when this 
trouble happens.

Not sure if it issue of libtorrent or qBittorrent or my router. I simple 
providing information... if it helps.

I also bad at English as you can see. Sorry.

Original comment by xstefm...@gmail.com on 6 Feb 2014 at 5:12

GoogleCodeExporter commented 9 years ago 
libtorrent 1.0 includes the reason for the blocked peer. (I can't change 0.16.x 
without breaking the ABI)

Original comment by arvid.no...@gmail.com on 28 Feb 2014 at 5:21