Discussion Forums > Technology
PeerBlock ~Effective IP Filter or Harmful~
dogsinafen:
--- Quote from: K7IA on June 07, 2010, 09:14:10 PM ---^ In fact this is some serious activity if the log entries are not connection retries etc which I can't tell since the src/dest ip addresses are concealed.
But may be I can assume these are indeed probes for infringement detection of copyright protected material if they originate from/to different ip addresses.
i.e if Euroaccess|Anti-p2p log entries are from a lot of different ip addresses, then the block is indeed protecting you. If it is from a single ip, the effectiveness assessment would probably be inconclusive.
You could drive some conclusions whether the software is helpful or not through simple logic just like this one.
--- End quote ---
Most of these anti p2p companies will not have a block of IPs since that cost money. Most of them have a few servers running that collect information on the peer pool. Thus only one IP is needed. Having a block of IPs and multiple servers on different IPs can get expensive. All they are doing is running a torrent and collecting the data they receive from the tracker updates and peers. You only need one server and one client to do that.
bloody000:
The obvious problem is that you are trusting the IP list and its maintainers. for all we know it could just be a BS list compile by anti-p2p orgs to give people a false sense of security.
K7IA:
--- Quote from: dogsinafen on June 07, 2010, 09:21:41 PM ---All they are doing is running a torrent and collecting the data they receive from the tracker updates and peers. You only need one server and one client to do that.
--- End quote ---
Yes that is correct if they only want to collect peer information like who is leeching/seeding the torrent. Technically you need only one client/tracker to acquire this information.
But P2P activities are often global data transactions, like someone seeding from Malaysia and someone leeching from Spain, so collecting information and enforcing law to these users might not be conventional. Instead they attempt to delay the propagation of material by injecting corrupted data during transmission. Fortunately this triggers individual banning of peers if the BitTorrent client (or any other P2P software) supports it, that is why a anti-P2P would probably need a pool of ip addresses. That's where imo IP range blocking come in handy. Let's not forget that a single machine can be configured to bind to multiple ip addresses.
DaggerLite:
--- Quote from: dogsinafen on June 07, 2010, 08:41:08 PM ---So using that application does help. The only strange problem I had was that the IP of my seedbox was being blocked because of OVHSAS was also hosted on the same network. But that was a simple fix.
--- End quote ---
This is a perfect example of what I mean about IP blocking doing harm. Since your seedbox, which we assume is a legit connection (note: this discussion is not about illegal sharing, so don't delve on that subject here), is hosted within the OVH SAS network, every single PeerBlock user with the standard Anti-P2P list is blocking your seedbox. I guess we can agree that it is in the interest of those people to connect to you, and that you're not trying to hack or spy on their activity. These blocklists may cover both safe and undesired IPs, but for the most part the safe ones get blocked.
Luckily for you, relatively few people seem to use IP blocking.
--- Quote from: K7IA on June 08, 2010, 11:13:12 AM ---But P2P activities are often global data transactions, like someone seeding from Malaysia and someone leeching from Spain, so collecting information and enforcing law to these users might not be conventional.
--- End quote ---
It is of course very possible for countries to work together on certain things like criminal activities. If notified, not much effort is needed for someone in Spain to check a torrent X.
K7IA:
--- Quote from: DaggerLite on June 08, 2010, 01:26:39 PM ---
--- Quote from: dogsinafen on June 07, 2010, 08:41:08 PM ---So using that application does help. The only strange problem I had was that the IP of my seedbox was being blocked because of OVHSAS was also hosted on the same network. But that was a simple fix.
--- End quote ---
This is a perfect example of what I mean about IP blocking doing harm. Since your seedbox, which we assume is a legit connection (note: this discussion is not about illegal sharing, so don't delve on that subject here), is hosted within the OVH SAS network, every single PeerBlock user with the standard Anti-P2P list is blocking your seedbox.
--- End quote ---
This is indeed a very good example of how it can be harmful. You would naturally manually alter your PeerBlock/etc ip list to permit connections to your seedbox, but other peers using PeerBlock will continue to block your seedbox.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version